cs-feat-design

Name: cs-feat-design
Availability: InStock
Author: liuzhengdong

Convert vague feature ideas into slug-design.md and slug-checklist.yaml files.

1.1k|82|Updated Apr 12, 2026

Search Tags:#design #architecture #documentation #requirements #roadmap #process #feature-design

Ready to run

npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-feat-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cs-feat-design
Source: https://github.com/liuzhengdongfortest/CodeStable/tree/main/cs-feat-design
Command: npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-feat-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting precise, review-ready feature designs is often time-consuming and error-prone. cs-feat-design provides a structured process to convert vague ideas and brainstorm notes into concrete slug-design.md documents and slug-checklist.yaml checklists, ensuring downstream implementers and QA share a single source of truth.

Core Features & Use Cases

Formal drafting: generate slug-design.md and slug-checklist.yaml from ready intents or brainstorm notes.
Initialization mode: create the feature directory with a skeleton {YYYY-MM-DD}-{slug} and an empty {slug}-intent.md.
Roadmap-backed starts: start from a roadmap item, wire it to the design and checklist, and update roadmap status and feature naming as needed.

Quick Start

Provide a feature slug and a brief context to generate slug-design.md and slug-checklist.yaml for immediate review.

Frequently Asked Questions about cs-feat-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I translate vague feature ideas into review-ready design blueprints?▼

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.

What is the best way to draft feature design documents from roadmap items?▼

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.

How do I generate a feature design checklist 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.

Can I initialize a feature directory with a skeleton design and intent file?▼

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.

Why do I need frontmatter metadata and decision constraints in a feature design?▼

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.

Does this structured feature design process work without external dependencies?▼

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.