spec-development

Plan branch-scoped specification work into implementation and testing checklists.

11|2|Updated Sep 8, 2015
One-click install
npx skills add https://github.com/jitrapon/astro-mobile --skill spec-development-jitrapon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-development
Source: https://github.com/jitrapon/astro-mobile/tree/main/.claude/skills/spec-development
Command: npx skills add https://github.com/jitrapon/astro-mobile --skill spec-development-jitrapon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a branch-owned specification into an executable plan, then guides the implementation, verification, and review loop so work lands in small, reviewable steps instead of drifting across the repo.

Core Features & Use Cases

  • Spec Planning: Reads the branch SPEC, drafts actionable checklists, and preserves the user-authored sections untouched.
  • Incremental Implementation: Resumes one unchecked item at a time, verifies it with the paired tests or checks, and marks progress only after evidence passes.
  • Adversarial Review Workflow: Runs the post-implementation review loop, triages findings, and helps decide whether to continue or finish the branch.
  • Use Case: If a team is building a KMP app feature from a branch spec, this Skill can structure the plan, implement the next task, validate it, and keep the review loop moving toward a clean handoff.

Quick Start

Use the spec-development skill to review the branch spec, execute the next unchecked task, and continue until the implementation and review checks are complete.

Frequently Asked Questions about spec-development

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

FAQPage Schema
How do I turn a branch specification into actionable implementation checklists?

Branch specification planning converts a SPEC.md file into executable implementation and testing checklists. It reads the branch spec, drafts actionable tasks, and preserves user-authored sections while structuring work into small, reviewable steps.

What is the best way to manage incremental implementation and verification on a single branch?

Incremental implementation and verification resumes one unchecked checklist item at a time, validates it with paired tests, and marks progress only after evidence passes. This ensures branch-scoped work lands in small steps with gated verification and commit discipline.

How does an adversarial review loop work for branch-scoped specification work?

An adversarial review loop runs post-implementation checks that triage findings and help decide whether to continue or finish the branch. It enforces repeatable review-loop handling and gated verification before branch completion to ensure clean handoffs.

Do I need a SPEC.md file to use branch-scoped iterative development?

Yes, branch-scoped iterative development requires a .claude/SPEC.md file in the repository. This file serves as the branch-owned specification that the planning process reads to draft actionable checklists and guide implementation.

Can I use branch specification planning for KMP app feature development?

Yes, branch specification planning applies to KMP app feature development. It structures the plan from a branch spec, implements the next task, validates it with paired tests, and keeps the review loop moving toward a clean handoff.

What are the limitations of checklist-driven branch development?

Checklist-driven branch development is limited to repositories using .claude/SPEC.md for iterative development on a single branch. It requires strict checklist management, gated verification, and commit discipline, making it unsuitable for multi-branch or spec-less workflows.