spec-tasking

Audit ANALYSIS.md spec coverage and generate a prioritized TODO.yaml.

23|2|Updated Jun 9, 2025
One-click install
npx skills add https://github.com/kaptinlin/gozod --skill spec-tasking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-tasking
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/spec-tasking
Command: npx skills add https://github.com/kaptinlin/gozod --skill spec-tasking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the ANALYSIS.md at the project root to verify spec coverage and generate a prioritized TODO.yaml for missing or incomplete specs. This ensures alignment between planned analyses and generated specification tasks, speeding up the spec-writing workflow.

Core Features & Use Cases

  • Audit Analysis: Reviews ANALYSIS.md to identify gaps between planned specs and existing SPECS files.
  • Task Generation: Produces one spec-writing task per missing or incomplete spec, ordered by the priority indicated in ANALYSIS.md.
  • Workflow Orchestration: Outputs a ready-to-run TODO.yaml that drives the spec-writing process and maintains traceability.

Quick Start

Run the skill at the project root to audit ANALYSIS.md and produce a complete TODO.yaml.

Frequently Asked Questions about spec-tasking

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

FAQPage Schema
How do I generate a TODO file from my project analysis document?

To generate a TODO file from your analysis document, the skill audits ANALYSIS.md at the project root to verify spec coverage and produces a prioritized TODO.yaml for missing or incomplete specs. It extracts planned analyses to create actionable specification tasks.

How do I audit spec coverage and identify missing specifications?

You audit spec coverage by comparing your ANALYSIS.md file against existing SPECS paths. This process identifies gaps between planned analyses and generated specifications, ensuring full traceability and alignment before generating any new spec-writing tasks.

What is the best way to automate spec-writing task generation for project management?

Automating spec-writing task generation involves reviewing ANALYSIS.md to find incomplete specs and outputting a ready-to-run TODO.yaml. This workflow orchestration file drives the spec-writing process by producing one prioritized task per missing specification.

Do I need research reports and SPECS files to generate a prioritized TODO.yaml?

Yes, you need corresponding .research reports and SPECS paths to generate a prioritized TODO.yaml. The skill requires these inputs at the project root to successfully verify spec coverage and produce a clean task list for the spec-writing workflow.

How are spec-writing tasks prioritized when generated from ANALYSIS.md?

Spec-writing tasks are prioritized based on the order indicated within your ANALYSIS.md file. The skill generates one task per missing or incomplete spec, outputting a TODO.yaml that maintains alignment with your planned project priorities.