technical-constitution

Software architecture planning enforces security and testing standards by generating a governance-aligned technical constitution. This produces a concrete plan with milestones, threat modeling strategies, and compliance verification criteria for robust error handling.

A technical constitution is a structured approach to generate and enforce architectural plans that align with governance standards. It captures architectural decisions, risks, and tradeoffs to maintain compliance across security, testing, and error-handling requirements.

Code refactoring aligns with SOLID and testability standards through compliance verification against critical architectural guidelines. This process validates modular design contracts and testability ports to ensure maintainable, independently testable codebases.

Yes, you can generate a compliance plan for input validation and threat modeling. The skill provides security-first guidance covering these areas alongside testing strategies and error handling standards to verify robust architectural compliance.

You need to provide a high-level task description like designing a new feature. The skill then scopes the task to architecture, security, testing, and error handling to produce a constitution-aligned technical plan with measurable milestones.

A governance-aligned architecture plan is necessary when starting implementation tasks or refactoring code that must maintain strict compliance. It ensures modular design with clear contracts and robust error handling rather than relying on informal decisions.