spec

Orchestrate spec-driven planning, phased implementation, and spec-aware code review.

42|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/scosman/vibe-crafting --skill spec-scosman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/scosman/vibe-crafting/tree/main/skill
Command: npx skills add https://github.com/scosman/vibe-crafting --skill spec-scosman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turns vague ideas into concrete engineering work by enforcing a structured loop: write specs, build in phases with review gates, and verify changes match the design.

Core Features & Use Cases

  • New project planning: Generates a project spec (overview → functional spec → architecture → implementation plan) and sets it as active work.
  • Phased autonomous implementation: Implements one or multiple phases with an agentic coding + spec-aware code review loop.
  • Task mode for quick changes: Executes small-to-medium updates without forcing full spec planning artifacts.
  • Spec-aware code review: Reviews local diffs against the active project/task specs, including deep multi-phase review for larger diffs.
  • GitHub PR feedback handling: Fetches unresolved PR review threads, routes them into the implement loop, and posts replies back to the PR.

Quick Start

Run /spec setup in the target repo, then start a spec-backed build with /spec new_project.

Frequently Asked Questions about spec

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

FAQPage Schema
What is spec-driven development and how does it structure software builds?

Spec-driven development enforces a structured loop: write specs, build in phases with review gates, and verify changes match the design. It transforms vague ideas into concrete engineering work by generating project, functional, and architecture specifications before autonomous implementation begins.

How do I start a new project using spec-driven planning?

To start a spec-driven build, run the setup command in your target repository to create the specs/projects structure and active-work state, then initiate a new project. The system generates an overview, functional spec, architecture, and implementation plan sequentially.

Can I execute one-off code changes without generating full architecture specs?

Yes, you can execute small-to-medium updates using task mode. This mode handles quick changes without forcing the full spec planning artifacts required for larger phased implementations, allowing faster iteration on minor repository updates.

How does spec-aware code review work for local diffs?

Spec-aware code review analyzes local diffs against active project or task specs. For larger diffs, it performs a deep multi-phase review to verify that code changes align with the functional specifications and architecture artifacts defined during planning.

Does this workflow integrate with GitHub PR feedback for autonomous agents?

Yes, the workflow fetches unresolved GitHub PR review threads, routes them into the implement loop for resolution, and posts replies back to the PR. This automates the feedback cycle within the phased implementation process.

What repository setup is required before implementing phased builds?

You need a repository setup that creates a specs/projects structure and active-work state. This environment is required to transition through planning, building, reviewing, committing, and addressing PR feedback during phased implementation.