feature

Implements spec-driven features through gated contract approval, TDD, review, and micro-commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an approved specification into shipped code without losing control: features are split into mini-features, each implemented one at a time with explicit approval gates, so nothing reaches a commit without contract sign-off, test review, and judge validation. ## Core Features & Use Cases - Contract-gated implementation: Requires an approved contract.md (Gate 1) before any code is written, and blocks on unresolved NEEDS CLARIFICATION items or stale amendments. - Per mini-feature pipeline: Coordinates pmo, dev agents, ui-designer, judge, security-reviewer, and mutation-tester subagents one at a time, with optional TDD (Gate 2 test approval) per slice. - Autonomy-aware micro-commits: Commits each finished mini-feature on a typed branch, pausing for diff review in gated mode and always requiring explicit confirmation for push, merge, and publish. - Use Case: Run /feature add CSV export to the holdings list to generate a spec and contract, approve it, then watch each mini-feature implemented, reviewed, and committed in dependency order. ## Quick Start Ask the agent to run /feature with a short description of the feature you want built, then approve the contract it produces.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I implement a feature with spec-driven development in Claude Code?▼

Run /feature with a description or tracked branch name. The skill generates or reuses a spec and contract, waits for your Gate 1 approval, then implements one mini-feature at a time with judge review and micro-commits on a typed branch.

How does TDD work in the /feature workflow?▼

When TDD is active, the implementer writes failing tests first and you approve them at Gate 2 before any production code is written. TDD can be skipped per mini-feature with "skip TDD" or enabled on request with "with TDD" when off by default.

What happens if the spec has unresolved NEEDS CLARIFICATION items?▼

The skill scans spec artifacts before Gate 1 and refuses implementation if any NEEDS CLARIFICATION lines remain, listing the unresolved questions. You must resolve them in the spec before the contract can be approved.

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

Use /fix for a small, scoped change with an obvious cause. It skips the spec, contract, and orchestration overhead but still enforces the full Definition of Done, while /feature is for larger work needing decomposition and gates.

Does /feature push or merge branches automatically?▼

No. Push, merge, and publish always require explicit confirmation regardless of autonomy mode. In gated mode it also pauses to present each diff before the micro-commit; in autonomous mode it commits and continues.