Generate a phase-based implementation spec with tasks and dependencies.
npx skills add https://github.com/Kabilan108/dotfiles --skill create-spec
Please help me install this Agent Skill. Skill: create-spec Source: https://github.com/Kabilan108/dotfiles/tree/main/agents/skills/create-spec Command: npx skills add https://github.com/Kabilan108/dotfiles --skill create-spec
This Skill converts vague project ideas into a concrete, phased specification that guides planning, discussion, and implementation, reducing ambiguity and back-and-forth.
Provide a project idea or description to the create-spec skill. It will generate a spec file (<project-name>/spec.md) using the references/spec-template.md as the guide.
High-intent search queries and answers about installing and using this skill.
To turn a rough idea into an actionable specification, provide your project description to generate a structured spec. The output uses a template to define concrete tasks, dependencies, and branch-name suggestions across Explore, Discuss, and Write phases.
A phase-based specification is a structured implementation plan that guides project development through Explore, Discuss, and Write stages. It reduces ambiguity by outlining concrete tasks and dependencies for each phase, ensuring clear planning and build execution.
Structure implementation specs for early-stage projects by using a template-driven output to organize tasks and dependencies. This generates a ready-to-refine spec file that breaks down the work into Explore, Discuss, and Write phases for clear execution.
Yes, generated spec files are designed to be ready-to-refine inputs for spec-interview or spec-driven-build workflows. The template-driven output creates a structured plan that directly supports downstream planning and discussion processes.
The best way to plan dependencies and branch names is to generate a phase-based spec from your project idea. This process automatically suggests a branch name and lists concrete dependencies for each stage of the implementation plan.
You should avoid using a template-driven spec when your project requires highly non-linear or exploratory workflows that cannot be structured into predefined Explore, Discuss, and Write phases. It is best suited for structured early-stage ideas and feature work.
mikeyobrienTransform rough ideas into design plans with requirements and research artifacts.
wukangcheng2944Interview users to refine implementation specs with explicit next steps.
murphyjosephEnforce project hygiene rules for dependencies, packaging, naming, and tooling.
duonghuan2122000Generate a dependency-ordered tasks.md from design artifacts.
