sdd-cli 0.1.2 → 0.1.4

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 (66) hide show
  1. package/README.md +126 -89
  2. package/dist/cli.js +7 -3
  3. package/dist/commands/doctor.js +11 -2
  4. package/dist/commands/gen-architecture.js +13 -3
  5. package/dist/commands/gen-best-practices.js +12 -2
  6. package/dist/commands/gen-functional-spec.js +13 -3
  7. package/dist/commands/gen-project-readme.js +14 -4
  8. package/dist/commands/gen-technical-spec.js +13 -3
  9. package/dist/commands/gen-utils.js +9 -1
  10. package/dist/commands/hello.js +21 -3
  11. package/dist/commands/learn-deliver.js +17 -3
  12. package/dist/commands/learn-refine.js +32 -11
  13. package/dist/commands/learn-start.js +9 -2
  14. package/dist/commands/learn-utils.js +7 -4
  15. package/dist/commands/pr-audit.js +17 -3
  16. package/dist/commands/pr-finish.js +17 -3
  17. package/dist/commands/pr-report.js +17 -3
  18. package/dist/commands/pr-respond.js +17 -3
  19. package/dist/commands/pr-start.js +9 -2
  20. package/dist/commands/pr-utils.js +8 -5
  21. package/dist/commands/req-archive.js +14 -6
  22. package/dist/commands/req-create.js +71 -14
  23. package/dist/commands/req-export.js +11 -3
  24. package/dist/commands/req-finish.js +26 -11
  25. package/dist/commands/req-lint.js +10 -2
  26. package/dist/commands/req-list.js +10 -2
  27. package/dist/commands/req-plan.js +33 -11
  28. package/dist/commands/req-refine.js +54 -5
  29. package/dist/commands/req-report.js +10 -2
  30. package/dist/commands/req-start.js +29 -12
  31. package/dist/commands/req-status.js +10 -2
  32. package/dist/commands/test-plan.js +13 -5
  33. package/dist/context/flags.d.ts +2 -0
  34. package/dist/context/flags.js +5 -1
  35. package/dist/providers/codex.js +2 -2
  36. package/dist/router/prompt-map.js +17 -5
  37. package/dist/ui/prompt.d.ts +1 -0
  38. package/dist/ui/prompt.js +8 -0
  39. package/dist/validation/gates.d.ts +19 -0
  40. package/dist/validation/gates.js +41 -0
  41. package/dist/validation/validate.js +24 -4
  42. package/dist/workspace/index.d.ts +6 -0
  43. package/dist/workspace/index.js +41 -10
  44. package/flows/ADMISSIONS_ADMIN.md +35 -33
  45. package/flows/ART.md +35 -33
  46. package/flows/COURT_SYSTEM.md +35 -33
  47. package/flows/DATA_SCIENTIST.md +35 -33
  48. package/flows/ECOMMERCE.md +35 -33
  49. package/flows/ECONOMICS.md +35 -33
  50. package/flows/GRAPHIC_DESIGN.md +35 -33
  51. package/flows/HISTORY.md +35 -33
  52. package/flows/LAWYER.md +36 -34
  53. package/flows/PROGRAMMER.md +35 -33
  54. package/flows/RETAIL_STORE.md +35 -33
  55. package/flows/SOCIOLOGY.md +35 -33
  56. package/flows/STATE_ADMIN.md +35 -33
  57. package/flows/STUDENT_UNIVERSITY.md +35 -33
  58. package/flows/TAXES_ADMIN.md +35 -33
  59. package/flows/TEACHER.md +35 -33
  60. package/package.json +13 -3
  61. package/router/BUSINESS.flow.md +59 -57
  62. package/router/DATA_SCIENCE.flow.md +60 -58
  63. package/router/DESIGN.flow.md +60 -58
  64. package/router/HUMANITIES.flow.md +60 -58
  65. package/router/LEGAL.flow.md +60 -58
  66. package/router/SOFTWARE_FEATURE.flow.md +61 -59
package/router/SOFTWARE_FEATURE.flow.md CHANGED
@@ -1,59 +1,61 @@
1
- # Router flow: Software feature
2
-
3
- ## Entry signals
4
- - "feature", "build", "implement", "API", "backend", "frontend"
5
-
6
- ## Steps
7
- 1) Run discovery and acceptance criteria prompts.
8
- 2) Generate requirements and functional spec.
9
- 3) Generate technical spec and architecture.
10
- 4) Ask for approval or `--improve`.
11
- 5) Activate quality profile and test plan.
12
-
13
- ## Required questions
14
- - What problem is solved and for whom?
15
- - What is in scope/out of scope?
16
- - What are acceptance criteria?
17
- - What performance/security constraints apply?
18
- - What is the rollout strategy?
19
-
20
- ## Required outputs
21
- - `requirement.md`
22
- - `functional-spec.md`
23
- - `technical-spec.md`
24
- - `architecture.md`
25
- - `test-plan.md`
26
- - `quality.yml`
27
-
28
- ## Scripted Q/A tree
29
-
30
- ### Q1: Problem and users
31
- Q: "What problem are we solving and for whom?"
32
- A: capture user/persona and objective
33
-
34
- ### Q2: Scope
35
- Q: "What is in scope and out of scope?"
36
- A: capture scope boundaries
37
-
38
- ### Q3: Acceptance criteria
39
- Q: "What are the acceptance criteria?"
40
- A: capture verifiable criteria
41
-
42
- ### Q4: Constraints
43
- Q: "Any performance, security, or compatibility constraints?"
44
- A: capture NFRs
45
-
46
- ### Q5: Rollout
47
- Q: "How should we rollout and measure success?"
48
- A: capture rollout + metrics
49
-
50
- ### Q6: Approval gate
51
- Q: "Approve requirements and move to specs?"
52
- A: Yes -> generate specs
53
- A: No -> refine
54
-
55
- ## Gates
56
- - No implementation without acceptance criteria and test plan
57
-
58
- ## Agents
59
- - Req Analyst, Solution Architect, Tech Lead, QA
1
+ # Router flow: Software feature
2
+
3
+ ## Entry signals
4
+ - "feature", "build", "implement", "API", "backend", "frontend"
5
+
6
+ ## Steps
7
+ 1) Run discovery and acceptance criteria prompts.
8
+ 2) Generate requirements and functional spec.
9
+ 3) Generate technical spec and architecture.
10
+ 4) Ask for approval or `--improve`.
11
+ 5) Activate quality profile and test plan.
12
+
13
+ ## Required questions
14
+ - What problem is solved and for whom?
15
+ - What is in scope/out of scope?
16
+ - What are acceptance criteria?
17
+ - What performance/security constraints apply?
18
+ - What is the rollout strategy?
19
+
20
+ ## Required outputs
21
+ - `requirement.md`
22
+ - `functional-spec.md`
23
+ - `technical-spec.md`
24
+ - `architecture.md`
25
+ - `test-plan.md`
26
+ - `quality.yml`
27
+
28
+ ## Scripted Q/A tree
29
+
30
+ ### Q1: Problem and users
31
+ Q: "What problem are we solving and for whom?"
32
+ A: capture user/persona and objective
33
+
34
+ ### Q2: Scope
35
+ Q: "What is in scope and out of scope?"
36
+ A: capture scope boundaries
37
+
38
+ ### Q3: Acceptance criteria
39
+ Q: "What are the acceptance criteria?"
40
+ A: capture verifiable criteria
41
+
42
+ ### Q4: Constraints
43
+ Q: "Any performance, security, or compatibility constraints?"
44
+ A: capture NFRs
45
+
46
+ ### Q5: Rollout
47
+ Q: "How should we rollout and measure success?"
48
+ A: capture rollout + metrics
49
+
50
+ ### Q6: Approval gate
51
+ Q: "Approve requirements and move to specs?"
52
+ A: Yes -> generate specs
53
+ A: No -> refine
54
+
55
+ ## Gates
56
+ - No implementation without acceptance criteria and test plan
57
+
58
+ ## Agents
59
+ - Req Analyst, Solution Architect, Tech Lead, QA
60
+
61
+