specs-dev

Coordinate plan-first development workflows with gate-based reviews and handoffs.

52|4|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/vaayne/agent-kit --skill specs-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specs-dev
Source: https://github.com/vaayne/agent-kit/tree/main/skills/specs-dev
Command: npx skills add https://github.com/vaayne/agent-kit --skill specs-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan-first development workflow that ensures requirements understanding, gating, and structured phased implementation with reviews to reduce rework and misalignment.

Core Features & Use Cases

  • Phase-driven planning with actionable tasks and built-in reviews
  • Gate-based progression to ensure approvals before execution
  • Handoff-rich phase summaries guiding subsequent work and audits

Quick Start

Start by drafting a plan for the feature, submit it for review, and proceed only after approval.

Frequently Asked Questions about specs-dev

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

FAQPage Schema
How does a plan-first development workflow reduce rework?

A plan-first development workflow reduces rework by imposing gate-based milestones for approvals and structured phased execution with reviews, ensuring requirements are understood before coding begins.

How do I implement review gates for feature implementation?

To implement review gates, draft a structured plan with actionable tasks, submit it for review, and proceed to the next execution phase only after receiving explicit approval at each gate.

Can I use this gated workflow for code refactoring instead of new features?

Yes, this gated workflow applies to refactoring or any task requiring structured planning. It generates phase-driven plans with handoff-rich summaries to guide subsequent work and audits.

What is the best way to manage handoffs during phased project execution?

The best way to manage handoffs is using a workflow that records phase summaries and gated reviews, ensuring approvals are documented and guiding subsequent work for audits.

When should I not use a gate-based development workflow?

You should avoid a gate-based development workflow for rapid prototyping or unstructured tasks where formal milestone approvals and phased planning would create unnecessary overhead.