spec

Converts ideas or tickets into approved specs, Given/When/Then contracts, and PR-sized mini-features.

3|Updated May 2, 2026
One-click install
npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill spec-juantrujillodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/JuanTrujilloDev/agent-config-template/tree/main/cursor/.claude/skills/spec
Command: npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill spec-juantrujillodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a raw idea, ticket, or SOW into implementable work often skips alignment, producing vague requirements and oversized pull requests. This Skill frames the problem through conversation, records decisions, and produces an approved contract before any code is written. ## Core Features & Use Cases - Conversational Spec Writing: Spawns a pmo agent that debates decisions and edge cases, then writes docs/specs/<slug>/spec.md with success criteria, open questions, and design notes. - Contract Generation: Distills Given/When/Then acceptance scenarios into contract.md and decomposes work into PR-sized mini-features tracked in features.json. - Approval Gate: Pauses at Gate 1 for explicit contract approval before implementation begins, and can mirror mini-features into your issue tracker. - Use Case: Run /spec add CSV export to the holdings list to turn a feature request into a reviewed spec, an acceptance contract, and a sequenced list of small implementation slices. ## Quick Start Ask the agent to run /spec followed by a description of the feature or ticket you want turned into an approved contract.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn a feature idea into an implementation plan?▼

Run /spec followed by your idea or ticket reference. The pmo agent converses with you about intent and edge cases, writes a spec with success criteria, decomposes the work into PR-sized mini-features, and pauses for your contract approval.

What files does the spec workflow generate?▼

It creates three files under docs/specs/<slug>/: spec.md with the problem, decisions, and design notes; contract.md with Given/When/Then acceptance scenarios; and features.json listing mini-features with size limits and pending status.

Can I use /spec with a tracked ticket from my issue tracker?▼

Yes, pass the ticket reference using your configured branch prefix, such as /spec PROJ-87. After decomposition, the skill can mirror the mini-features back into your tracker as subtasks or as a comment on the main task.

When should I use /fix instead of /spec?▼

Use /fix for a small, scoped change with an obvious root cause that does not need a contract. Use /spec whenever work requires framing, open questions, or decomposition into multiple implementation slices.

What happens after I approve the contract at Gate 1?▼

Once you approve the contract, run /feature. It picks up the approved spec and implements the mini-features one at a time, keeping each change within the declared file and line-of-code limits.