cs-roadmap

Decomposes large requirements into architecture plans and ordered sub-feature roadmaps.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/wildlily1021/XW_Software --skill cs-roadmap-wildlily1021
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cs-roadmap
Source: https://github.com/wildlily1021/XW_Software/tree/main/.agents/skills/cs-roadmap
Command: npx skills add https://github.com/wildlily1021/XW_Software --skill cs-roadmap-wildlily1021

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large requirements that cannot fit into a single feature often get implemented ad hoc, causing inconsistent interfaces and duplicated work. This Skill turns an oversized requirement into a complete upfront plan: a module-level design, executable interface contracts, and a dependency-ordered list of sub-features stored under codestable/roadmap/. ## Core Features & Use Cases - Two modes (new / update): Create a new roadmap for a big requirement, or update an existing one by adding sub-features, reordering, or marking items dropped. - Architecture-first decomposition: Produces a module breakdown plus interface contracts written to function-signature, data-structure, and error-code level, which downstream feature design must treat as hard constraints. - Machine-readable tracking: Generates an items.yaml with slug, description, depends_on, status, and minimal-loop flags, validated with validate-yaml.py and synced with the feature lifecycle. - Use Case: A user says "I want a permission system." The Skill drafts a roadmap with RBAC core, admin UI, and audit sub-features, defines the permission-check API contract, marks the minimal end-to-end loop, and hands each item to the feature workflow. ## Quick Start Ask the AI to break down a large requirement into a roadmap, for example: "Help me decompose the notification center requirement into a roadmap with module design and sub-features."

Frequently Asked Questions about cs-roadmap

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

FAQPage Schema
How do I break down a large software requirement into features?▼

Start with the architecture: define module boundaries and responsibilities first, then write interface contracts between modules, and only then split the work into sub-features. Each sub-feature must be able to complete an independent design-implement-accept cycle.

What should a feature roadmap document contain?▼

A roadmap should contain background, scope with explicit exclusions, a module breakdown, interface contracts at function-signature and error-code level, an ordered sub-feature list with dependencies, scheduling rationale, and open observations for the user.

When should I use a roadmap instead of a single feature design?▼

Use a roadmap when the requirement clearly cannot fit in one feature, such as adding a permission system or notification center. If a single feature can hold the work, go directly to feature design instead.

How are dependencies between sub-features validated?▼

Dependencies are recorded in items.yaml as depends_on lists referencing other items in the same roadmap. The dependency graph must be a DAG with no cycles, and each dependency needs a concrete reason such as a shared table or API.

What are the limitations of roadmap-level planning?▼

Roadmaps stop at module boundaries and interface contracts; they do not specify internal implementation details of individual features. They also do not modify requirements or architecture documents, which only record current system state.