feature-designer

This Skill automates drafting a structured design.md for architecture decisions. It enforces a standardized template covering goals, current state, data models, interfaces, and acceptance criteria to align stakeholders and reduce rework.

A design.md file should include sections for goals, current state, data models, interfaces, and acceptance criteria. This Skill enforces these standardized sections to ensure comprehensive documentation for module specifications and design rationale.

Standardize architecture documentation by applying this Skill to enforce a unified design-report template. It ensures consistency and completeness across all design docs, helping teams start from a common structure for backend and frontend tasks.

Yes, this Skill applies to documenting architecture decisions for both frontend and backend modules. It generates a design.md that captures context, constraints, and proposed architecture to ensure comprehensive module specifications.

The best way to align stakeholders is to generate a design.md capturing context, constraints, and proposed architecture. This Skill produces a ready-to-use design report with standardized sections to ensure everyone starts from a common understanding.