new-task

Execute SPEC.md and PLAN.md implementation in isolated git worktrees with TDD.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/smp4/claude-skills --skill new-task-smp4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-task
Source: https://github.com/smp4/claude-skills/tree/main/dot_claude/skills/new-task
Command: npx skills add https://github.com/smp4/claude-skills --skill new-task-smp4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork from taking a SPEC.md and PLAN.md through implementation by orchestrating the entire workflow within an isolated git worktree, which keeps the main checkout untouched and ensures every change is traceable to a documented requirement.

Core Features & Use Cases

  • Automated worktree setup: Detects the repo state, derives feature slug, creates a feature branch, and commits an empty starting point so every unit runs in a clean environment.
  • Strict TDD execution: Parses PLAN.md units, writes tests-first, follows red-green-refactor, verifies against SPEC.md, and commits each unit with requirement traces and test counts.
  • Verification, docs, and submission: Generates VERIFICATION.md, audits project docs for drift, syncs updates, posts GitHub issue comments if applicable, and pushes or merges the feature branch for final review.
  • Use Case: When a user says “/new-task dev-docs/user-auth/,” the Skill loads the plan, runs each unit (optionally with --unit or --continuous), and hands off results or submits via PR.

Quick Start

Ask the assistant to run /new-task with your dev-docs/feature path so it loads the SPEC.md and PLAN.md, creates the worktree, and begins the red-green-refactor cycle.

Frequently Asked Questions about new-task

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

FAQPage Schema
How do I automate TDD execution from a SPEC.md and PLAN.md in my repository?▼

To automate TDD execution from SPEC.md and PLAN.md, the Skill parses your plan units, creates an isolated git worktree, and enforces a strict red-green-refactor cycle. It verifies acceptance criteria against your spec and commits each unit with requirement traces.

How does git worktree isolation keep my main branch untouched during implementation?▼

Git worktree isolation keeps the main branch untouched by deriving a feature slug, creating a dedicated feature branch, and committing an empty starting point in a separate directory. This ensures every test and code change runs in a clean, traceable environment without affecting your primary checkout.

What is the best way to run specific implementation units from a local docs directory?▼

The best way to run specific implementation units from a local docs directory is by invoking the task with your dev-docs path and optional flags like --unit. This loads the SPEC.md and PLAN.md, sets up the worktree, and targets only the specified units, or runs continuously with --continuous.

Do I need a GitHub issue to use this automated spec verification workflow?▼

You do not need a GitHub issue to use this automated spec verification workflow. The Skill operates when planning artifacts come from either a GitHub issue or a local docs directory, traversing unit targets and posting issue comments only if applicable to your repository state.

How do I sync project documentation after completing a red-green-refactor cycle?▼

To sync project documentation after a red-green-refactor cycle, the Skill audits your existing docs for drift, generates a VERIFICATION.md file, and syncs updates. It then pushes or merges the feature branch via PR or commit according to your current repo state.