cs-feat-design

To translate vague feature ideas into review-ready design blueprints, you provide a feature slug and brief context to generate structured slug-design.md documents and slug-checklist.yaml checklists. This enforces frontmatter metadata, decision constraints, and dependencies for deterministic reviews.

Drafting feature design documents from roadmap items involves starting from a roadmap entry, wiring it to the design and checklist, and updating roadmap status and feature naming. This produces concrete slug-design.md files and slug-checklist.yaml files for downstream implementers and QA.

You generate a feature design checklist by providing a ready intent or brainstorm notes to produce a slug-checklist.yaml file. This checklist ensures downstream implementers and QA share a single source of truth by enforcing dependencies and mounting points for seamless handoffs.

Yes, you can initialize a feature directory using an initialization mode that creates a skeleton directory named with {YYYY-MM-DD}-{slug} and an empty {slug}-intent.md file. This provides a structured starting point for formal drafting and review-ready design blueprints.

Frontmatter metadata and decision constraints are needed in a feature design to enable deterministic reviews and seamless handoffs. Enforcing these elements within the slug-design.md document ensures downstream implementers and QA share a single source of truth.

Yes, this structured feature design process works without external dependencies. It operates independently to convert ready intents or brainstorm notes into concrete slug-design.md documents and slug-checklist.yaml checklists, requiring only a feature slug and brief context to start.