Capture project blueprints and feature specifications into Markdown files.
npx skills add https://github.com/m19803261706/cx-workflow --skill cx-scope
Please help me install this Agent Skill. Skill: cx-scope Source: https://github.com/m19803261706/cx-workflow/tree/main/skills/cx-scope Command: npx skills add https://github.com/m19803261706/cx-workflow --skill cx-scope
This Skill helps clarify project direction and feature specifics early in the development lifecycle, preventing scope creep and ensuring alignment before detailed planning begins.
/cx-scope to discuss and document the project's overall goals, target audience, and key features. For a specific new feature, use /cx-scope {feature_name} to hash out its requirements and technical approach.Initiate a discussion about the overall project scope by typing /cx-scope.
High-intent search queries and answers about installing and using this skill.
Defining project scope requires multi-turn dialogue to capture positioning, target users, functional modules, and technical boundaries. This Skill facilitates that discussion, documenting the resulting project blueprint and feature details locally in Markdown files.
Preventing scope creep involves clarifying project direction and feature specifics early. You can discuss and document the overall vision, target audience, and core modules beforehand to ensure alignment before detailed planning begins.
Yes, project blueprints and feature definitions can be synced to GitHub Issues. After capturing the project positioning and technical boundaries, the Skill optionally syncs the documented specifications directly to your repository.
Gathering requirements for a specific feature involves hashing out its goals, user flows, and technical approach. You can initiate a targeted discussion by providing the feature name, which captures the specific requirements and boundaries.
Yes, project scoping integrates an Explore subagent to scan your existing project structure and technology stack. This provides necessary technical context to accurately define feature boundaries and specifications during the dialogue.
Project blueprints and feature scopes are saved in local Markdown files. This ensures the documented project vision, functional modules, and priorities are stored in a portable, readable format for your development lifecycle.
telum-aiCreate a Speck project structure with a skeleton project.md file.
bRRRITSCOLDAutomate GitHub issue creation and management from implementation plans.
HardyLiu6Turn raw ideas into detailed design specifications through structured dialogue.
antinomyhqGenerate structured Markdown implementation plans with validation steps.