spec

Convert GitHub issue requirements into implementation plans with acceptance criteria.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/saitoco/wholework --skill spec-saitoco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/saitoco/wholework/tree/main/skills/spec
Command: npx skills add https://github.com/saitoco/wholework --skill spec-saitoco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Issue Specification reads Issue requirements and creates an actionable implementation plan. It automatically adjusts investigation depth (light/full) based on Size and supports overrides to tailor depth.

Core Features & Use Cases

  • Reads Issue requirements and converts them into a concrete spec with steps, notes, and acceptance criteria.
  • Determines the investigation depth (light/full) from the issue Size, with override flags (--light or --full).
  • Integrates with worktrees, label transitions, blocking checks, steering documents, and domain loaders to produce and validate the spec.

Quick Start

Run the spec workflow on a target issue to generate a detailed implementation plan.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I convert GitHub issues into an actionable implementation plan?

To convert GitHub issues into an implementation plan, read the issue requirements and translate them into a verifiable spec with notes, steps, and acceptance criteria. This workflow integrates with worktrees and steering documents to produce a depth-aware actionable plan.

What is the best way to automate issue specification for a large codebase?

Automating issue specification involves dynamically determining investigation depth from issue size to generate actionable plans. By reading issue requirements and integrating with domain loaders, the system produces a verifiable spec with acceptance criteria tailored to the codebase.

How does investigation depth affect the generated implementation spec?

Investigation depth affects the spec by adjusting the analysis thoroughness based on issue size. Light depth provides a faster overview, while full depth ensures comprehensive validation through blocking checks and steering documents, resulting in a more detailed implementation plan.

Can I override the automatic investigation depth when planning codebase changes?

Yes, you can override the automatic investigation depth when planning codebase changes. Use the --light flag for a faster analysis or the --full flag to force comprehensive validation, ensuring the generated spec matches your required level of detail.

How do I validate acceptance criteria before starting codebase implementation?

To validate acceptance criteria before implementation, integrate blocking checks and steering documents into the specification workflow. This translates issue requirements into a verifiable spec, ensuring the generated plan meets all defined criteria and passes domain loader validation.

Does issue specification work with worktrees and label transitions?

Yes, issue specification works with worktrees and label transitions to produce and validate the spec. It integrates these components alongside GitHub issues and steering documents to ensure the implementation plan is verifiable and correctly tracks the workflow state.