specdacular 0.8.0 → 0.9.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (30) hide show
  1. package/README.md +166 -54
  2. package/commands/specd/continue.md +22 -14
  3. package/commands/specd/toolbox.md +58 -14
  4. package/package.json +1 -1
  5. package/specdacular/HELP.md +70 -9
  6. package/specdacular/STATE-MACHINE.md +376 -0
  7. package/specdacular/pipeline.json +76 -0
  8. package/specdacular/references/brain-routing.md +168 -0
  9. package/specdacular/references/commit-code.md +9 -6
  10. package/specdacular/references/commit-docs.md +9 -6
  11. package/specdacular/references/execute-hooks.md +127 -0
  12. package/specdacular/references/load-context.md +10 -9
  13. package/specdacular/references/resolve-pipeline.md +74 -0
  14. package/specdacular/references/select-feature.md +12 -5
  15. package/specdacular/references/validate-task.md +19 -11
  16. package/specdacular/templates/context/review-diff.md +60 -0
  17. package/specdacular/templates/context/section-display.md +51 -0
  18. package/specdacular/workflows/brain.md +378 -0
  19. package/specdacular/workflows/context-add.md +242 -0
  20. package/specdacular/workflows/context-manual-review.md +410 -0
  21. package/specdacular/workflows/continue.md +17 -259
  22. package/specdacular/workflows/execute.md +15 -42
  23. package/specdacular/workflows/map-codebase.md +14 -0
  24. package/specdacular/workflows/new.md +2 -2
  25. package/specdacular/workflows/phase-plan.md +142 -0
  26. package/specdacular/workflows/plan.md +10 -37
  27. package/specdacular/workflows/research.md +25 -7
  28. package/specdacular/workflows/review.md +11 -136
  29. package/specdacular/workflows/revise.md +126 -0
  30. package/specdacular/workflows/status.md +1 -1
@@ -0,0 +1,126 @@
1
+ <purpose>
2
+ Collect user feedback on review findings and create fix plans in decimal phases. Extracted from review.md — revise handles the "what to fix" conversation while review handles pure inspection.
3
+
4
+ **Output:** Fix plan in decimal phase directory (e.g., phase-01.1/PLAN.md), updated ROADMAP.md, config.json signaling for brain routing.
5
+ </purpose>
6
+
7
+ <philosophy>
8
+
9
+ ## Fix Plans, Not Inline Fixes
10
+
11
+ When the user reports issues, create proper PLAN.md files in decimal phases. These get executed through the same execute workflow.
12
+
13
+ ## Clear Signal to Brain
14
+
15
+ After creating a fix plan, signal the brain by setting `phases.current_status: "pending"` so the brain routes back to execute for the current phase.
16
+
17
+ </philosophy>
18
+
19
+ <process>
20
+
21
+ <step name="validate">
22
+ @~/.claude/specdacular/references/validate-task.md
23
+
24
+ Use extended validation. Check phases and ROADMAP exist.
25
+
26
+ Continue to load_context.
27
+ </step>
28
+
29
+ <step name="load_context">
30
+ @~/.claude/specdacular/references/load-context.md
31
+
32
+ Load all context including the current phase's PLAN.md and review findings.
33
+
34
+ **Read phase info:**
35
+ ```bash
36
+ PHASE_NUM=$(cat $TASK_DIR/config.json | grep -o '"current": [0-9]*' | grep -o '[0-9]*')
37
+ PHASE_DIR="$TASK_DIR/phases/phase-$(printf '%02d' $PHASE_NUM)"
38
+ cat "$PHASE_DIR/PLAN.md"
39
+ ```
40
+
41
+ Continue to collect_feedback.
42
+ </step>
43
+
44
+ <step name="collect_feedback">
45
+ Gather specific feedback from user.
46
+
47
+ ```
48
+ Tell me what needs fixing. You can describe:
49
+ - Bugs or incorrect behavior
50
+ - Approach you'd prefer changed
51
+ - Missing functionality
52
+ - Code quality issues
53
+
54
+ Describe as many issues as you want — I'll create a fix plan for all of them.
55
+ ```
56
+
57
+ Wait for user response. Follow up to understand each issue clearly.
58
+
59
+ Continue to create_fix_plan.
60
+ </step>
61
+
62
+ <step name="create_fix_plan">
63
+ Create a fix plan in a decimal phase.
64
+
65
+ **Determine fix phase number:**
66
+ ```bash
67
+ CURRENT=$(printf '%02d' $PHASE_NUM)
68
+ ls -d $TASK_DIR/phases/phase-$CURRENT.* 2>/dev/null | sort -V | tail -1
69
+ ```
70
+ - If no decimal phases → create `phase-{N}.1/`
71
+ - If `phase-{N}.1/` exists → create `phase-{N}.2/`, etc.
72
+
73
+ **Create fix phase directory and PLAN.md:**
74
+ ```bash
75
+ mkdir -p $TASK_DIR/phases/phase-{N.M}/
76
+ ```
77
+
78
+ Write `PLAN.md` using standard plan format:
79
+ - Objective: Address review feedback for Phase {N}
80
+ - Tasks: One per issue reported, with clear fix description and verification
81
+
82
+ **Update ROADMAP.md:**
83
+ Add fix phase entry after the parent phase.
84
+
85
+ Continue to signal_outcome.
86
+ </step>
87
+
88
+ <step name="signal_outcome">
89
+ Signal the brain that a fix plan was created and needs execution.
90
+
91
+ **Update config.json:**
92
+ - Set `phases.current_status` to `"pending"` — this tells the brain to route back to execute for the current phase (which will pick up the decimal fix phase)
93
+
94
+ Continue to commit.
95
+ </step>
96
+
97
+ <step name="commit">
98
+ @~/.claude/specdacular/references/commit-docs.md
99
+
100
+ - **$FILES:** fix plan directory + ROADMAP.md + config.json
101
+ - **$MESSAGE:** `docs({task-name}): create fix plan phase-{N.M}`
102
+ - **$LABEL:** `fix plan`
103
+
104
+ Continue to completion.
105
+ </step>
106
+
107
+ <step name="completion">
108
+ Present what was created.
109
+
110
+ ```
111
+ Fix plan created: phase-{N.M}
112
+ {count} tasks to address review feedback.
113
+ ```
114
+
115
+ End workflow (caller handles continuation).
116
+ </step>
117
+
118
+ </process>
119
+
120
+ <success_criteria>
121
+ - User feedback collected with clear understanding of issues
122
+ - Fix plan created in decimal phase directory
123
+ - ROADMAP.md updated with fix phase
124
+ - config.json signals brain to route back to execute
125
+ - Changes committed
126
+ </success_criteria>
@@ -29,7 +29,7 @@ cat .specd/config.json 2>/dev/null
29
29
 
30
30
  ### 3. Check for features directory
31
31
 
32
- Use Glob to check if `.specd/tasks/*/config.json` matches anything.
32
+ Use Glob to check if `.specd/tasks/*/config.json` or `.specd/features/*/config.json` matches anything (check both for backwards compatibility).
33
33
 
34
34
  **If mode = orchestrator and no root features:**
35
35
  Also check sub-project features — scan each project path for `{project-path}/.specd/tasks/*/config.json`. If features found in sub-projects, continue (there's something to show).