Skip to content

feat: add modular builder workflow with intent architect and contract authoring - #15

Merged
Brian Krabach (bkrabach) merged 1 commit into
mainfrom
modular-amplifier
Sep 18, 2025
Merged

feat: add modular builder workflow with intent architect and contract authoring#15
Brian Krabach (bkrabach) merged 1 commit into
mainfrom
modular-amplifier

Conversation

@bkrabach

Copy link
Copy Markdown
Collaborator

Introduces a comprehensive modular builder system for Claude Code that enables
one-command module generation from natural language requirements. This workflow
follows a disciplined Contract → Spec → Plan → Generate → Review pattern.

Key additions:

  • /modular-build command: CLI interface for module generation workflow
  • module-intent-architect agent: Translates natural language to module specs
  • contract-spec-author agent: Creates formal Contract and Implementation specs
  • CONTRACT_SPEC_AUTHORING_GUIDE: Comprehensive guide for authoring specs
  • MODULAR_BUILDER_LITE docs: User-facing documentation
  • README updates: Integration with main documentation

The system enforces strict isolation where workers only read their module's
contract/spec plus dependency contracts, ensuring clean boundaries and
regeneratable modules following the "bricks and studs" philosophy.

… authoring
Introduces a comprehensive modular builder system for Claude Code that enables
one-command module generation from natural language requirements. This workflow
follows a disciplined Contract → Spec → Plan → Generate → Review pattern.
Key additions:
- /modular-build command: CLI interface for module generation workflow
- module-intent-architect agent: Translates natural language to module specs
- contract-spec-author agent: Creates formal Contract and Implementation specs
- CONTRACT_SPEC_AUTHORING_GUIDE: Comprehensive guide for authoring specs
- MODULAR_BUILDER_LITE docs: User-facing documentation
- README updates: Integration with main documentation
The system enforces strict isolation where workers only read their module's
contract/spec plus dependency contracts, ensuring clean boundaries and
regeneratable modules following the "bricks and studs" philosophy.
@bkrabach
Brian Krabach (bkrabach) merged commit 8c7e3f1 into mainSep 18, 2025
1 check passed
Michael J. Jabbour (michaeljabbour) added a commit to michaeljabbour/amplifier that referenced this pull request Sep 30, 2025
Complete comprehensive technical specification library with all 44 principles:
**People (6 specs)**
- #1 Small AI-first working groups
- #2 Strategic human touchpoints only
- #3 Prompt engineering as core skill
- microsoft#4 Test-based verification over code review
- microsoft#5 Conversation-driven development
- microsoft#6 Human escape hatches always available
**Process (13 specs)**
- microsoft#7 Regenerate, don't edit
- microsoft#8 Contract-first everything
- microsoft#9 Tests as the quality gate
- microsoft#10 Git as safety net
- microsoft#11 Continuous validation with fast feedback
- microsoft#12 Incremental processing as default
- microsoft#13 Parallel exploration by default
- microsoft#14 Context management as discipline
- microsoft#15 Git-based everything
- microsoft#16 Docs define, not describe
- microsoft#17 Prompt versioning and testing
- microsoft#18 Contract evolution with migration paths
- microsoft#19 Cost and token budgeting
**Technology (18 specs)**
- microsoft#20 Self-modifying AI-first codebase
- microsoft#21 Limited and domain-specific by design
- microsoft#22 Layered virtualization
- microsoft#23 Protected self-healing kernel
- microsoft#24 Long-running agent processes
- microsoft#25 Simple interfaces by design
- microsoft#26 Stateless by default
- microsoft#27 Disposable components everywhere
- microsoft#28 CLI-first design
- microsoft#29 Tool ecosystems as extensions
- microsoft#30 Observability baked in
- microsoft#31 Idempotency by design (reference)
- microsoft#32 Error recovery patterns built in
- microsoft#33 Graceful degradation by design
- microsoft#34 Feature flags as deployment strategy
- microsoft#35 Least-privilege automation
- microsoft#36 Dependency pinning and security scanning
- microsoft#37 Declarative over imperative
**Governance (7 specs)**
- microsoft#38 Access control and compliance
- microsoft#39 Metrics and evaluation everywhere
- microsoft#40 Knowledge stewardship and institutional memory
- microsoft#41 Adaptive sandboxing with explicit approvals
- microsoft#42 Data governance and privacy controls
- microsoft#43 Model lifecycle management
- microsoft#44 Self-serve recovery with known-good snapshots
Each specification includes:
- Plain-language definition
- AI-first development rationale
- 4-6 implementation approaches
- 5 good/bad example pairs with working code
- 6 related principles with relationships
- 7 common pitfalls with examples
- Tools organized by category
- 12 actionable checklist items
Statistics:
- 44 specifications totaling ~10,000+ lines
- 220+ good/bad code example pairs
- 240+ implementation approaches
- 300+ documented anti-patterns
- 500+ tools and frameworks
- 250+ cross-principle relationships
Created through parallel AI agent execution demonstrating
Principle microsoft#13 (Parallel Exploration by Default).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Joi Ito (Joi) pushed a commit to Joi/amplifier that referenced this pull request Oct 31, 2025
… authoring (microsoft#15)
Introduces a comprehensive modular builder system for Claude Code that enables
one-command module generation from natural language requirements. This workflow
follows a disciplined Contract → Spec → Plan → Generate → Review pattern.
Key additions:
- /modular-build command: CLI interface for module generation workflow
- module-intent-architect agent: Translates natural language to module specs
- contract-spec-author agent: Creates formal Contract and Implementation specs
- CONTRACT_SPEC_AUTHORING_GUIDE: Comprehensive guide for authoring specs
- MODULAR_BUILDER_LITE docs: User-facing documentation
- README updates: Integration with main documentation
The system enforces strict isolation where workers only read their module's
contract/spec plus dependency contracts, ensuring clean boundaries and
regeneratable modules following the "bricks and studs" philosophy.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@bkrabach