Skip to content

Documentation for SDD 2.0 clarifying the Git integration and providing workflow examples for requirement changes at different stages #52

@AndreyMalykhin

Description

@AndreyMalykhin

Hey guys, I couldn’t find in the docs whether (or when) you need to use Git and commit changes in order to use the --refine argument for both plan and implement. SKILL.md mentions using a Git diff, though.

It’d also be great to document:

  • more real-world scenarios for what to do when requirements change at different stages (e.g., after /implement).
  • whether you need to clear context (e.g., Claude Code /clear) before running /plan or /implement.
  • whether you need to use /plan or /implement again after the conversation compaction process (e.g. Claude Code /compact).
  • whether every prompt in a conversation needs to be prefixed with /plan or /implement. For example:
    /add-task -> /plan -> /implement -> /implement I've changed my mind -> /implement I've changed my mind again
    vs
    /add-task -> /plan -> /implement -> I've changed my mind -> I've changed my mind again

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions