sdd-cli 0.1.0 → 0.1.3

package/flows/TEACHER.md

@@ -1,33 +1,34 @@
-# Flow: Teacher (education)
-
-## Goal
-Create a system for lesson planning, assessments, and feedback with clear learning outcomes.
-
-## Discovery prompts
-- What grade levels and subjects are supported?
-- What is the grading model (rubrics, points, mastery)?
-- How are students and guardians notified?
-- Are there accessibility requirements?
-- What data privacy rules apply to students?
-
-## Required artifacts
-- `requirement.md` with learning objectives and scope
-- `functional-spec.md` covering lesson, assignment, and grading flows
-- `technical-spec.md` for integrations (LMS, email, calendars)
-- `architecture.md` for content storage and versioning
-- `test-plan.md` with grading accuracy and accessibility checks
-
-## Risk and compliance
-- Student data privacy
-- Accessibility standards
-- Content versioning and auditability
-
-## Acceptance criteria examples
-- Teachers can reuse and version lessons.
-- Students receive feedback within configured SLAs.
-- Accessibility checks are enforced for uploaded content.
-
-## Recommended outputs
-- Lesson plan templates
-- Grading rubric engine
-- Student progress analytics
+# Flow: Teacher (education)
+
+## Goal
+Create a system for lesson planning, assessments, and feedback with clear learning outcomes.
+
+## Discovery prompts
+- What grade levels and subjects are supported?
+- What is the grading model (rubrics, points, mastery)?
+- How are students and guardians notified?
+- Are there accessibility requirements?
+- What data privacy rules apply to students?
+
+## Required artifacts
+- `requirement.md` with learning objectives and scope
+- `functional-spec.md` covering lesson, assignment, and grading flows
+- `technical-spec.md` for integrations (LMS, email, calendars)
+- `docs/ARCHITECTURE.md` for content storage and versioning
+- `test-plan.md` with grading accuracy and accessibility checks
+
+## Risk and compliance
+- Student data privacy
+- Accessibility standards
+- Content versioning and auditability
+
+## Acceptance criteria examples
+- Teachers can reuse and version lessons.
+- Students receive feedback within configured SLAs.
+- Accessibility checks are enforced for uploaded content.
+
+## Recommended outputs
+- Lesson plan templates
+- Grading rubric engine
+- Student progress analytics
+

package/package.json

@@ -1,9 +1,17 @@
 {
-  "name": "sdd-cli",
-  "version": "0.1.0",
+  "name": "sdd-cli",
+  "version": "0.1.3",
   "description": "SDD-first, AI-native CLI for end-to-end delivery.",
+  "homepage": "https://github.com/jdsalasca/sdd-cli#readme",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/jdsalasca/sdd-cli.git"
+  },
+  "bugs": {
+    "url": "https://github.com/jdsalasca/sdd-cli/issues"
+  },
   "bin": {
-    "sdd-tool": "dist/cli.js",
+    "sdd-cli": "dist/cli.js",
     "sdd": "dist/cli.js"
   },
   "main": "dist/cli.js",
@@ -18,7 +26,9 @@
   "scripts": {
     "build": "tsc -p tsconfig.json",
     "start": "node dist/cli.js",
-    "dev": "ts-node src/cli.ts"
+    "dev": "ts-node src/cli.ts",
+    "pretest": "npm run build",
+    "test": "node --test tests/*.test.js"
   },
   "dependencies": {
     "ajv": "^8.17.1",

package/router/BUSINESS.flow.md

@@ -1,57 +1,58 @@
-# Router flow: Business / economics
-
-## Entry signals
-- "market", "pricing", "policy", "forecast", "economics"
-
-## Steps
-1) Interview for objective, scope, and stakeholders.
-2) Define assumptions and model approach.
-3) Generate analysis plan and outputs.
-4) Ask for approval or `--improve`.
-5) Produce sensitivity checks and executive summary.
-
-## Required questions
-- What decision will this analysis support?
-- What scope and timeframe apply?
-- What data sources are available?
-- What assumptions are acceptable?
-- What risk tolerance is required?
-
-## Required outputs
-- `requirement.md`
-- `technical-spec.md`
-- `architecture.md`
-- `test-plan.md` (sensitivity checks)
-
-## Scripted Q/A tree
-
-### Q1: Decision
-Q: "What decision will this analysis support?"  
-A: capture decision context
-
-### Q2: Scope and timeline
-Q: "What scope and timeframe apply?"  
-A: capture scope and horizon
-
-### Q3: Data sources
-Q: "What data sources are available and trusted?"  
-A: capture sources
-
-### Q4: Assumptions
-Q: "What assumptions are acceptable?"  
-A: capture assumptions
-
-### Q5: Risk tolerance
-Q: "What level of risk or uncertainty is acceptable?"  
-A: capture tolerance
-
-### Q6: Approval gate
-Q: "Approve analysis plan and move to specs?"  
-A: Yes -> generate specs  
-A: No -> refine
-
-## Gates
-- Assumptions must be explicit before analysis
-
-## Agents
-- Analyst, Economist, Critic
+# Router flow: Business / economics
+
+## Entry signals
+- "market", "pricing", "policy", "forecast", "economics"
+
+## Steps
+1) Interview for objective, scope, and stakeholders.
+2) Define assumptions and model approach.
+3) Generate analysis plan and outputs.
+4) Ask for approval or `--improve`.
+5) Produce sensitivity checks and executive summary.
+
+## Required questions
+- What decision will this analysis support?
+- What scope and timeframe apply?
+- What data sources are available?
+- What assumptions are acceptable?
+- What risk tolerance is required?
+
+## Required outputs
+- `requirement.md`
+- `technical-spec.md`
+- `docs/ARCHITECTURE.md`
+- `test-plan.md` (sensitivity checks)
+
+## Scripted Q/A tree
+
+### Q1: Decision
+Q: "What decision will this analysis support?"  
+A: capture decision context
+
+### Q2: Scope and timeline
+Q: "What scope and timeframe apply?"  
+A: capture scope and horizon
+
+### Q3: Data sources
+Q: "What data sources are available and trusted?"  
+A: capture sources
+
+### Q4: Assumptions
+Q: "What assumptions are acceptable?"  
+A: capture assumptions
+
+### Q5: Risk tolerance
+Q: "What level of risk or uncertainty is acceptable?"  
+A: capture tolerance
+
+### Q6: Approval gate
+Q: "Approve analysis plan and move to specs?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- Assumptions must be explicit before analysis
+
+## Agents
+- Analyst, Economist, Critic
+

package/router/DATA_SCIENCE.flow.md

@@ -1,58 +1,59 @@
-# Router flow: Data science
-
-## Entry signals
-- "model", "prediction", "dataset", "ML", "analytics"
-
-## Steps
-1) Interview for objective, metrics, data sources, constraints.
-2) Define evaluation criteria and monitoring needs.
-3) Generate specs and architecture for pipelines.
-4) Ask for approval or `--improve`.
-5) Create test plan for data validation and model evaluation.
-
-## Required questions
-- What is the success metric?
-- What data sources and quality risks exist?
-- What fairness or compliance rules apply?
-- What latency/cost constraints exist?
-- How will drift be monitored?
-
-## Required outputs
-- `requirement.md`
-- `technical-spec.md`
-- `architecture.md`
-- `test-plan.md`
-- `quality.yml`
-
-## Scripted Q/A tree
-
-### Q1: Objective and metric
-Q: "What is the business or research objective and the primary metric?"  
-A: capture target metric
-
-### Q2: Data sources
-Q: "What data sources exist and what are the quality risks?"  
-A: capture sources and gaps
-
-### Q3: Constraints
-Q: "Any latency, cost, or compliance constraints?"  
-A: capture constraints
-
-### Q4: Fairness and bias
-Q: "Any fairness or bias concerns to monitor?"  
-A: capture fairness criteria
-
-### Q5: Monitoring
-Q: "How will we monitor drift post-release?"  
-A: capture monitoring plan
-
-### Q6: Approval gate
-Q: "Approve requirements and move to specs?"  
-A: Yes -> generate specs  
-A: No -> refine
-
-## Gates
-- Metrics and validation criteria required before plan
-
-## Agents
-- Data Scientist, MLOps, QA
+# Router flow: Data science
+
+## Entry signals
+- "model", "prediction", "dataset", "ML", "analytics"
+
+## Steps
+1) Interview for objective, metrics, data sources, constraints.
+2) Define evaluation criteria and monitoring needs.
+3) Generate specs and architecture for pipelines.
+4) Ask for approval or `--improve`.
+5) Create test plan for data validation and model evaluation.
+
+## Required questions
+- What is the success metric?
+- What data sources and quality risks exist?
+- What fairness or compliance rules apply?
+- What latency/cost constraints exist?
+- How will drift be monitored?
+
+## Required outputs
+- `requirement.md`
+- `technical-spec.md`
+- `docs/ARCHITECTURE.md`
+- `test-plan.md`
+- `quality.yml`
+
+## Scripted Q/A tree
+
+### Q1: Objective and metric
+Q: "What is the business or research objective and the primary metric?"  
+A: capture target metric
+
+### Q2: Data sources
+Q: "What data sources exist and what are the quality risks?"  
+A: capture sources and gaps
+
+### Q3: Constraints
+Q: "Any latency, cost, or compliance constraints?"  
+A: capture constraints
+
+### Q4: Fairness and bias
+Q: "Any fairness or bias concerns to monitor?"  
+A: capture fairness criteria
+
+### Q5: Monitoring
+Q: "How will we monitor drift post-release?"  
+A: capture monitoring plan
+
+### Q6: Approval gate
+Q: "Approve requirements and move to specs?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- Metrics and validation criteria required before plan
+
+## Agents
+- Data Scientist, MLOps, QA
+

package/router/DESIGN.flow.md

@@ -1,58 +1,59 @@
-# Router flow: Design / creative
-
-## Entry signals
-- "logo", "brand", "UI", "layout", "visual", "art"
-
-## Steps
-1) Interview for goals, audience, references, constraints.
-2) Define deliverables and review cadence.
-3) Generate requirements and design system structure.
-4) Ask for approval or `--improve`.
-5) Produce delivery checklist and accessibility checks.
-
-## Required questions
-- What is the message or brand?
-- Who is the audience?
-- What formats are needed?
-- What constraints or references exist?
-- What is the approval process?
-
-## Required outputs
-- `requirement.md`
-- `functional-spec.md`
-- `technical-spec.md`
-- `architecture.md`
-- `test-plan.md`
-
-## Scripted Q/A tree
-
-### Q1: Message and audience
-Q: "What is the message and who is the audience?"  
-A: capture audience and goal
-
-### Q2: Deliverables
-Q: "What formats are required (logo, web, print, social)?"  
-A: capture deliverables
-
-### Q3: References
-Q: "Any style references or inspirations?"  
-A: capture references
-
-### Q4: Constraints
-Q: "What constraints apply (timeline, budget, tools)?"  
-A: capture constraints
-
-### Q5: Approval cadence
-Q: "Who approves and how often should we review?"  
-A: capture review cadence
-
-### Q6: Approval gate
-Q: "Approve requirements and move to specs?"  
-A: Yes -> generate specs  
-A: No -> refine
-
-## Gates
-- Deliverables and approval process must be defined
-
-## Agents
-- Creative Lead, Design Systems, Critic
+# Router flow: Design / creative
+
+## Entry signals
+- "logo", "brand", "UI", "layout", "visual", "art"
+
+## Steps
+1) Interview for goals, audience, references, constraints.
+2) Define deliverables and review cadence.
+3) Generate requirements and design system structure.
+4) Ask for approval or `--improve`.
+5) Produce delivery checklist and accessibility checks.
+
+## Required questions
+- What is the message or brand?
+- Who is the audience?
+- What formats are needed?
+- What constraints or references exist?
+- What is the approval process?
+
+## Required outputs
+- `requirement.md`
+- `functional-spec.md`
+- `technical-spec.md`
+- `docs/ARCHITECTURE.md`
+- `test-plan.md`
+
+## Scripted Q/A tree
+
+### Q1: Message and audience
+Q: "What is the message and who is the audience?"  
+A: capture audience and goal
+
+### Q2: Deliverables
+Q: "What formats are required (logo, web, print, social)?"  
+A: capture deliverables
+
+### Q3: References
+Q: "Any style references or inspirations?"  
+A: capture references
+
+### Q4: Constraints
+Q: "What constraints apply (timeline, budget, tools)?"  
+A: capture constraints
+
+### Q5: Approval cadence
+Q: "Who approves and how often should we review?"  
+A: capture review cadence
+
+### Q6: Approval gate
+Q: "Approve requirements and move to specs?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- Deliverables and approval process must be defined
+
+## Agents
+- Creative Lead, Design Systems, Critic
+

package/router/HUMANITIES.flow.md

@@ -1,58 +1,59 @@
-# Router flow: Humanities research
-
-## Entry signals
-- "history", "sociology", "philosophy", "essay", "thesis"
-
-## Steps
-1) Interview for thesis, scope, sources, and format.
-2) Define structure and methodology.
-3) Generate plan and section outline.
-4) Ask for approval or `--improve`.
-5) Produce reading list and source checks.
-
-## Required questions
-- What is the thesis or research question?
-- What scope and timeframe apply?
-- What source types are acceptable?
-- What format is required?
-- What perspectives must be included?
-
-## Required outputs
-- `requirement.md`
-- `functional-spec.md`
-- `technical-spec.md` (citation rules)
-- `architecture.md` (structure)
-- `test-plan.md` (bias and source checks)
-
-## Scripted Q/A tree
-
-### Q1: Thesis
-Q: "What is the thesis or research question?"  
-A: capture thesis
-
-### Q2: Scope
-Q: "What period, region, or population is in scope?"  
-A: capture scope boundaries
-
-### Q3: Sources
-Q: "What sources are acceptable or required?"  
-A: capture source types and citation style
-
-### Q4: Format
-Q: "What output format is required?"  
-A: capture format
-
-### Q5: Perspectives
-Q: "Which perspectives must be included?"  
-A: capture perspectives
-
-### Q6: Approval gate
-Q: "Approve research plan and move to structure?"  
-A: Yes -> generate specs  
-A: No -> refine
-
-## Gates
-- Thesis and scope required before deep research
-
-## Agents
-- Researcher, Critic, Synthesizer
+# Router flow: Humanities research
+
+## Entry signals
+- "history", "sociology", "philosophy", "essay", "thesis"
+
+## Steps
+1) Interview for thesis, scope, sources, and format.
+2) Define structure and methodology.
+3) Generate plan and section outline.
+4) Ask for approval or `--improve`.
+5) Produce reading list and source checks.
+
+## Required questions
+- What is the thesis or research question?
+- What scope and timeframe apply?
+- What source types are acceptable?
+- What format is required?
+- What perspectives must be included?
+
+## Required outputs
+- `requirement.md`
+- `functional-spec.md`
+- `technical-spec.md` (citation rules)
+- `docs/ARCHITECTURE.md` (structure)
+- `test-plan.md` (bias and source checks)
+
+## Scripted Q/A tree
+
+### Q1: Thesis
+Q: "What is the thesis or research question?"  
+A: capture thesis
+
+### Q2: Scope
+Q: "What period, region, or population is in scope?"  
+A: capture scope boundaries
+
+### Q3: Sources
+Q: "What sources are acceptable or required?"  
+A: capture source types and citation style
+
+### Q4: Format
+Q: "What output format is required?"  
+A: capture format
+
+### Q5: Perspectives
+Q: "Which perspectives must be included?"  
+A: capture perspectives
+
+### Q6: Approval gate
+Q: "Approve research plan and move to structure?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- Thesis and scope required before deep research
+
+## Agents
+- Researcher, Critic, Synthesizer
+