Framework for spec-driven software development with AI agent teams on Claude Code.
# Clone the framework
git clone https://github.com/mikall/FactoryX.git ~/.sdd-framework
chmod +x ~/.sdd-framework/install.shcd /path/to/your/project
~/.sdd-framework/install.sh "ProjectName" # 1. Initialize project structure
claude # 2. Open Claude Code
# Then inside Claude Code:
# /project-bootstrap # 3. Process your intake materialsDrop your project materials (docs, specs, notes, screenshots) into
intake/before or after running the installer.
cd /path/to/your/project
claude # 1. Open Claude Code directly
# Then inside Claude Code:
# /project-bootstrap # 2. It detects missing setup, runs the installer, then asks you to restart
/project-bootstrapauto-detects if the project hasn't been initialized and runs the installer for you. You'll need to restart Claude Code once after the first setup so the skills are loaded.
/project-bootstrap → Process intake/ into structured project context
/sprint-planning → Plan the first sprint
/requirements-analysis → Detail requirements
/sprint-execution → Develop and test
/quick-fix → Quick bug fixes
/help → Check project status and suggested next step
| Agent | Role | Activation |
|---|---|---|
product-manager |
Prioritization, roadmap, metrics | Always |
solution-architect |
Architecture, ADR, technical decisions | Always |
spec-analyst |
Atomic requirements, testability | Always |
ux-designer |
User flows, usability, accessibility, design system | Per project type |
senior-test-engineer |
QA, E2E testing, quality metrics | Always |
code-reviewer |
Adversarial review, security | Always |
security-privacy-auditor |
Security audit, privacy, GDPR | Always |
| Skill | Type | Description |
|---|---|---|
/project-bootstrap |
Setup | Processes unstructured intake/ into structured context |
/sprint-planning |
CR | Multi-agent sprint planning |
/requirements-analysis |
CR | Requirements analysis + clarity gate |
/sprint-execution |
CR | Development + review + test + audit |
/quick-fix |
BF | Bug fix with scope detection |
/help |
Any | Inspects project state, suggests next step |
| Checklist | Reference |
|---|---|
| Clarity Gate | Stream Coding, Spec Kit |
| Security | OWASP Top 10 |
| Privacy | GDPR |
| Performance | Web Vitals, DB tuning |
| Accessibility | WCAG 2.1 AA |
Structured documents inspired by BABOK, PMBOK, modern agile frameworks, and Spec-Driven Development best practices (BMAD, Spec Kit, Stream Coding). Includes risk register, C4-based HLA, and DevOps deployment guidance.
| Skill | Description |
|---|---|
/devops-setup |
CI/CD pipeline generation, deployment scripts, monitoring setup. Pipeline scripts are produced during sprint execution; this skill will provide structured automation and refinement guidance. |
Clarity, simplicity, elegance, and economy in solutions are the most evident form of seniority.
- Simplicity: the simplest solution that works
- Economy: less code = fewer bugs = more reliability
- Performance: design constraint, not future optimization
- Spec-Driven: specs lead, code follows
- Testability: every component testable in isolation
- Change Request (CR): value increment, full cycle spec→code→test
- Bug Fix (BF): corrective maintenance, lightweight process, no spec changes
- Tier 1 - Standard: any structured product (default)
- Tier 2 - Governed: sensitive data, heavy compliance, regulated industries
- BMAD Method (multi-agent, adversarial review, scale-adaptive)
- GitHub Spec Kit (constitution, clarity checklists, cross-artifact analysis)
- Stream Coding (clarity gate, anti-patterns, document architecture)
- Clarity Gate (epistemic verification, pre-ingestion quality checks)
- C4 Model (zoomable architecture documentation)
- arc42 (crosscutting concepts, pragmatic documentation)
- ISO 31000 (risk management)
- BABOK (requirements engineering, traceability)
- PMBOK (project governance, quality management)
- Agile/Scrum (sprint cycle, iterative delivery)
- Shape Up (appetite-based planning, hill charts)
- SRE (error budgets, observability)
Special thanks to Francesco Marinoni Moretto for Stream Coding and Clarity Gate — two projects that significantly influenced this framework's approach to documentation-driven development and epistemic quality.
Contributions are welcome! Please open an issue to discuss proposed changes before submitting a pull request.
This project is licensed under the Apache License 2.0 — see the LICENSE file for details.