specimin-task

Decompose per-branch plans into atomic TDD-compliant tasks.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/timsvoice/specimin --skill specimin-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specimin-task
Source: https://github.com/timsvoice/specimin/tree/main/.claude-plugin/skills/specimin-task
Command: npx skills add https://github.com/timsvoice/specimin --skill specimin-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning often stays high-level. This Skill breaks plans into atomic, test-driven tasks that map to concrete files and functions, enabling precise execution and traceability.

Core Features & Use Cases

  • Plan decomposition: identify components, data structures, and integration points.
  • TDD-first tasks: create tests before implementation steps.
  • Traceability: assign tasks to exact plan items and acceptance criteria.

Quick Start

Invoke the task generator for the current branch: specimin-task.

Frequently Asked Questions about specimin-task

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

FAQPage Schema
How do I break down a high-level plan into atomic tasks for coding?

Plan decomposition converts high-level goals into atomic, executable tasks mapped to specific files and functions. This Skill analyzes your plan structure, identifies components and data structures, and generates test-driven task items with exact traceability to acceptance criteria, enabling precise agent execution.

What does test-driven task generation mean for implementation?

TDD-first task generation creates test specifications before implementation steps. Each task includes test cases that define expected behavior upfront, ensuring implementation focuses on passing concrete tests rather than ambiguous requirements.

How do I organize plans so the task generator can process them?

Store branch-specific plans under .specimin/plans/{branch} with plan.md containing high-level goals and spec.md defining technical requirements. The task generator loads this structure, validates initialization, and decomposes content into stage-accurate work items following a Stage 1 to Stage 4 workflow.

Can I use this for existing projects without restructuring?

The task generator requires initialized branch directories with plan.md and spec.md files. If your branch lacks these, the Skill returns explicit error handling and guidance; you'll need to set up the directory structure before task generation can proceed.

What happens if my plan is incomplete or ambiguous?

The Skill includes a clarification stage that analyzes plan structure and flags ambiguities before generating tasks. This prevents downstream execution errors by surfacing missing context or conflicting requirements early in the decomposition workflow.