Generate design artifacts and enforce architectural constraints for feature specifications.
npx skills add https://github.com/eavichay/mycli --skill spec-plan-eavichay
Please help me install this Agent Skill. Skill: spec-plan Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/spec-plan Command: npx skills add https://github.com/eavichay/mycli --skill spec-plan-eavichay
This Skill eliminates ambiguity in the software development lifecycle by enforcing a structured, template-driven approach to technical planning and design.
Execute the spec-plan skill to initialize the planning workflow for the current feature specification.
High-intent search queries and answers about installing and using this skill.
You can standardize technical planning by using a template-driven workflow to generate design artifacts, data models, and interface contracts from feature specifications. This enforces architectural constraints and ensures consistency before implementation begins.
The best way to transition a feature specification is through an automated workflow that performs research, defines data models, and establishes interface contracts. This generates a comprehensive implementation plan with actionable tasks based on your unified constitution.
Yes, enforcing architectural constraints requires a project structure compliant with the spec-kit framework and direct access to the repository constitution. These prerequisites provide the foundational rules and templates needed to gate the workflow.
Yes, you can automate the creation of research documents and data models by orchestrating a structured planning workflow. It generates these design artifacts automatically based on your repository's constitution and feature specifications.
Structured technical planning eliminates ambiguity by enforcing a template-driven approach that acts as a gatekeeper. It performs constitution checks to verify architectural consistency, ensuring all design artifacts and contracts align before any coding starts.
You need to run constitution checks during the technical implementation planning phase, right before development begins. This gatekeeping step verifies that generated design artifacts, data models, and interface contracts adhere to your architectural constraints.
NUMU-IOGenerate spec-kit bootstrap artifacts for existing brownfield repositories.
kimen-devGenerate dependency-ordered task lists from project design artifacts.
lync-cyberConverts PRD requirements into modules, APIs, data models, and non-functional decisions.
estaciolimaGenerates design artifacts, research documentation, and interface contracts for technical implementation planning in spec-kit projects.
