v0.1 bf7c821

plan.md RawHistoryFolder

Plan how to implement the specified feature.

This is the second step in the Spec-Driven Development lifecycle.

Given the implementation details provided as an argument, do this:

  1. Run scripts/setup-plan.sh --json from the repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. All future file paths must be absolute.

  2. Read and analyze the feature specification to understand:

    • The feature requirements and user stories
    • Functional and non-functional requirements
    • Success criteria and acceptance criteria
    • Any technical constraints or dependencies mentioned

  3. Read the constitution at /memory/constitution.md to understand constitutional requirements.

  4. Execute the implementation plan template:

    • Load /templates/plan-template.md (already copied to IMPL_PLAN path)
    • Set Input path to FEATURE_SPEC
    • Run the Execution Flow (main) function steps 1-10
    • The template is self-contained and executable
    • Follow error handling and gate checks as specified
    • Let the template guide artifact generation in $SPECS_DIR:
      • Phase 0 generates research.md
      • Phase 1 generates data-model.md, contracts/, quickstart.md
      • Phase 2 generates tasks.md
    • Incorporate user-provided details from arguments into Technical Context: $ARGUMENTS
    • Update Progress Tracking as you complete each phase

  5. Verify execution completed:

    • Check Progress Tracking shows all phases complete
    • Ensure all required artifacts were generated
    • Confirm no ERROR states in execution

  6. Report results with branch name, file paths, and generated artifacts.

Use absolute paths with the repository root for all file operations to avoid path issues.

source
1
2Plan how to implement the specified feature.
3
4This is the second step in the Spec-Driven Development lifecycle.
5
6Given the implementation details provided as an argument, do this:
7
81. Run `scripts/setup-plan.sh --json` from the repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. All future file paths must be absolute.
92. Read and analyze the feature specification to understand:
10   - The feature requirements and user stories
11   - Functional and non-functional requirements
12   - Success criteria and acceptance criteria
13   - Any technical constraints or dependencies mentioned
14
153. Read the constitution at `/memory/constitution.md` to understand constitutional requirements.
16
174. Execute the implementation plan template:
18   - Load `/templates/plan-template.md` (already copied to IMPL_PLAN path)
19   - Set Input path to FEATURE_SPEC
20   - Run the Execution Flow (main) function steps 1-10
21   - The template is self-contained and executable
22   - Follow error handling and gate checks as specified
23   - Let the template guide artifact generation in $SPECS_DIR:
24     * Phase 0 generates research.md
25     * Phase 1 generates data-model.md, contracts/, quickstart.md
26     * Phase 2 generates tasks.md
27   - Incorporate user-provided details from arguments into Technical Context: $ARGUMENTS
28   - Update Progress Tracking as you complete each phase
29
305. Verify execution completed:
31   - Check Progress Tracking shows all phases complete
32   - Ensure all required artifacts were generated
33   - Confirm no ERROR states in execution
34
356. Report results with branch name, file paths, and generated artifacts.
36
37Use absolute paths with the repository root for all file operations to avoid path issues.

Keyboard shortcuts

Single-key shortcuts are on. ctrl k and esc work whatever this says.

ctrl k :
go to a section, branch, tag, file or repository
?
this list
j k
move the row cursor down / up
enter
open the row under the cursor; on Files, a directory opens or closes in place
↑ ↓ ← → home end
in the file tree (focus on a row): previous / next row, close / open a directory or go to its parent / first entry, first / last row. They never open a file
l h
on Files: open a directory or a file / close a directory or go up to its parent, then to the parent page. Elsewhere: into the side panel (on a merge request, its files) / back to the content; there j k move between its controls
g g G
first / last row
/
filter the list; on Files, find a file anywhere in the repository (esc clears, enter opens the best match)
b
switch branch or tag
g s g f g c g b g m g i g r g a
tabs: summary, files, commits, branches & tags, merge requests, issues, releases, actions (when available)
g h
home
w
wide mode: use the whole width of the screen, or not (remembered)
y
copy a permalink pinned to the commit
d u x
diff: split / unified / collapse or expand all
e E
diff: the whole file in view / every file, with the lines the hunks hide
n
merge request: next note in the diff
esc
close a dialog, leave a field

Branches 8

Tags 42

↑↓ moveenter openesc close