mad-plan

To generate a technical implementation plan from a feature specification, provide the specification and a project constitution to produce phase-gated plans with research documentation, data models, API contracts, and verification specifications.

Architecture governance validation is the process of checking implementation plans against constitutional constraints and pattern compliance rules, ensuring coverage requirements are met before development teams begin building.

You can create API contracts and data models from specifications by transforming technology-agnostic feature specs into comprehensive technical implementation plans that automatically generate these artifacts alongside architecture diagrams.

Yes, a project constitution is required to generate implementation plans, as it provides the constitutional constraints and architectural standards used to enforce governance and validate pattern compliance during plan generation.

The best way to enforce pattern compliance across development teams is to validate generated implementation plans against constitutional constraints and coverage requirements before implementation begins, ensuring consistency and architectural adherence.

Yes, implementation planning can include review gates and coverage verification by generating phase-gated plans with agent context updates, ensuring implementation teams have verified specifications before building features.