spec-kitty

Enforce spec.md and plan.md generation before coding in feature workflows.

7|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/rloisell/rl-agents-n-skills --skill spec-kitty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kitty
Source: https://github.com/rloisell/rl-agents-n-skills/tree/main/spec-kitty
Command: npx skills add https://github.com/rloisell/rl-agents-n-skills --skill spec-kitty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

spec-first development enforces writing a formal spec and plan before coding, ensuring a consistent foundation for features and reducing rework.

Core Features & Use Cases

  • Enforces spec-first workflows by requiring spec.md, plan.md, and WP task definitions before implementation.
  • Generates and validates WP task templates, tracks progress through the planned→done lifecycle, and supports task-level traceability.
  • Use Case: teams starting a new feature generate a spec.md with requirements, a plan.md outlining phases, and WP tasks to organize work.

Quick Start

Create a new feature specification by drafting spec.md and plan.md, then generate atomic WP tasks before any implementation.

Frequently Asked Questions about spec-kitty

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

FAQPage Schema
How do I enforce spec-first development workflows before coding starts?

Spec-first development workflows are enforced by requiring a formal spec.md, plan.md, and task definitions before any implementation begins. This ensures a consistent foundation for features and reduces rework by validating plans upfront.

What is a spec-first development workflow and when do I need it?

A spec-first development workflow requires writing a formal specification and plan before coding to reduce rework. You need it when starting new feature development projects to ensure a consistent foundation and track progress through planned tasks.

How do I generate and validate WP tasks for feature development?

To generate and validate WP tasks, draft a spec.md with requirements and a plan.md outlining phases first. The workflow then generates atomic WP task templates, tracks their lifecycle from planned to done, and supports task-level traceability.

Does spec-first planning work without dependencies or external components?

Yes, spec-first planning works without dependencies or external components. The workflow autonomously validates spec.md sections, plan.md sections, and WP task formats using built-in validation checks, requiring no external setup.

What is the best way to organize feature work using spec and plan files?

The best way to organize feature work is creating a spec.md with requirements, a plan.md outlining phases, and atomic WP tasks to organize work. This structure tracks progress through the planned to done lifecycle with task-level traceability.

Why does my feature development lack traceability from plan to implementation?

Feature development lacks traceability when WP tasks are not generated from a formal spec.md and plan.md. Enforcing spec-first workflows generates WP task templates and tracks the planned to done lifecycle to ensure task-level traceability.