skills.rest
taxmaxi
taxmaxiOFFICIAL
Explore all skills by this author →
Website𝕏@TaxMaxiHQGitHub

spec

Rewrites a gap issue into a delivery spec with checklist using GitHub CLI.

1|1|Updated May 11, 2026
Search Tags:#planning#adr#github issues#spec#technical specification#gh cli#delivery checklist
One-click install
npx skills add https://github.com/taxmaxi/taxmaxi --skill spec-taxmaxi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/taxmaxi/taxmaxi/tree/main/.agents/skills/spec
Command: npx skills add https://github.com/taxmaxi/taxmaxi --skill spec-taxmaxi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a loosely defined gap issue into an actionable engineering spec is slow and inconsistent. This Skill upgrades a GitHub issue in place into a structured spec with a delivery checklist, following your repository's own process documentation. ## Core Features & Use Cases - In-place issue upgrade: Rewrites the issue body via gh issue edit, keeping the issue number and swapping needs-triage for ready-for-agent. - Grounded synthesis: Gathers context from the issue, conversation, research notes, grilling outcomes, and the codebase instead of interviewing the user. - Delivery checklist generation: Cuts one-PR-per-checkbox tasks with acceptance behavior, seams, decisions, and a final Harvest task, per the rules in docs/agents/delivery-process.md. - Use Case: After grounding and grilling are done on gap issue #247, run the spec workflow to rewrite it into a reviewer-ready spec with mermaid diagrams, ADR references, and an absorb step for related gap issues. ## Quick Start Run the spec skill with the issue number, for example /spec 247, to upgrade that gap issue into a full delivery spec.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn a GitHub issue into an engineering spec?▼

Run the spec workflow with the issue number, for example /spec 247. It reads the issue and its comments, grounds itself in the codebase, then rewrites the issue body following the spec template in docs/agents/delivery-process.md.

What must happen before running the spec workflow?▼

The definition lane's grounding and grilling must be complete. If one-way-door decisions that only the maintainer can answer remain open, the workflow stops and lists them instead of writing the spec.

Does the spec skill create a new issue or edit the existing one?▼

It edits the existing issue in place using gh issue edit, keeping the issue number and title. It swaps the needs-triage label for ready-for-agent and posts one comment noting the upgrade.

How is the delivery checklist structured?▼

Each checkbox maps to one PR targeting 5-8 files, carrying its acceptance behavior, result classification, seam, and decisions. Verification tasks name exact values, deletion tasks require maintainer approval, and the final task is always the Harvest.

What happens to other gap issues covered by the spec?▼

Each absorbed gap issue is closed with a comment saying absorbed into the spec's issue number, and all absorbed issues are listed in the spec's Problem section.

Related Skills

Explore More Software Engineering Skills→
bcbeidelbcbeidel
1

reversibility

Classify decisions as one-way or two-way doors to calibrate analysis effort.

Community
Intermediate
AlmogMaayanAlmogMaayan

ptp-writing-plans

Writes ordered, verifiable, agent-executable task checkboxes for a decided change.

Community
Intermediate
haryelramalhoharyelramalho

domain-modeling

Creates CONTEXT.md glossaries and ADR files documenting architectural decisions and vocabulary per bounded context.

Community
Advanced
smallnestsmallnest
207

ship-it

Commit changes, create and merge a pull request, and close the linked GitHub issue.

Community
Advanced