spec-gap-tasking

Audit ANALYSIS.md gaps and generate Phase 2 TODO.yaml tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts a gap-analysis report (ANALYSIS.md) into a structured TODO.yaml by pairing Plan+Execute tasks with Quality Review checkpoints for each identified gap after validating against the codebase.

Core Features & Use Cases

  • Audits ANALYSIS.md to confirm gap validity against the repository, updating status as needed.
  • Generates a Phase 2 TODO.yaml that encodes Plan/Execute tasks and Quality Review checkpoints for each identified gap.
  • Enforces that only items marked as ❌ or ⚠️ in the audited ANALYSIS.md are transformed into tasks, with correct task templates and dependencies.
  • Supports optional integration with spec-gap-analyzing outputs and aligns with governance for task planning.

Quick Start

Run the spec-gap-analyzing tool to produce ANALYSIS.md, then run this skill to generate TODO.yaml from gaps.

Frequently Asked Questions about spec-gap-tasking

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

FAQPage Schema
How do I convert a gap analysis report into actionable TODO tasks?▼

To convert a gap analysis report into actionable TODO tasks, audit your ANALYSIS.md to validate gaps against the codebase, then generate a TODO.yaml encoding Plan+Execute tasks and Quality Review checkpoints for each confirmed gap.

How do I generate a TODO.yaml from an ANALYSIS.md file?▼

You generate a TODO.yaml from an ANALYSIS.md file by running an automated audit that verifies identified gaps against the actual codebase, transforming only items marked as ❌ or ⚠️ into structured task entries with dependencies.

What is the best way to automate project task planning from a codebase gap analysis?▼

Automating project task planning from a gap analysis involves auditing ANALYSIS.md to confirm gap validity, then producing a Phase 2 TODO.yaml that pairs actionable Plan+Execute tasks with mandatory Quality Review checkpoints for each item.

Can I create TODO tasks from analysis gaps that are marked with warning symbols?▼

Yes, you can create TODO tasks from analysis gaps marked with warning symbols. The process strictly transforms only items marked as ❌ or ⚠️ in the audited ANALYSIS.md into structured tasks following prescribed templates.

Does this gap analysis tasking approach require a specific analysis file format?▼

Yes, this approach requires an ANALYSIS.md file as input. It audits this specific gap-analysis report to verify issues against the repository before generating the corresponding Phase 2 TODO.yaml with task templates.

Why are some gaps in my analysis report not converted into TODO tasks?▼

Gaps in your analysis report are not converted into TODO tasks because the process enforces that only items explicitly marked as ❌ or ⚠️ in the audited ANALYSIS.md are transformed into structured Plan+Execute tasks.