spec

Manages Spec-Driven Development artifacts through init, bootstrap, fill, check, and archive subcommands.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill spec-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/spec
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill spec-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces a disciplined Spec-Driven Development workflow where every feature spec is gated on an open GitHub issue, preventing untracked work and ensuring proposals, tasks, and verification artifacts stay consistent before and after implementation. ## Core Features & Use Cases - Spec scaffolding (init): Creates specs/<feature-id>/ from vault templates, gated on an open GitHub issue per ADR-018, with strict feature-id validation. - Socratic proposal filling (fill): Guides the user through structured questions to capture Why, What, Out of scope, Risks, and Acceptance criteria, tagging agent-drafted content for review. - Pre-implementation lint (check): Cross-checks acceptance criteria against tasks.md to detect uncovered criteria and orphan tasks before coding starts. - Archive with promotion (archive): Requires a passing adversarial review, then interactively promotes lessons, ADRs, and patterns before moving the spec to specs/archive/ and closing the GitHub issue. - Use Case: When planning a ~120 LOC change that touches a deployed config schema, the agent proactively proposes /spec init, walks you through the proposal, lints task coverage, and archives the spec only after an independent review passes. ## Quick Start Ask the agent to create a spec for your feature by saying "create a spec for <feature-id>" and provide the open GitHub issue number that gates the work.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I create a spec for a new feature?

Run /spec init <feature-id> with an open GitHub issue number via --issue. The skill validates the feature id, verifies the issue is open as a work gate, and scaffolds proposal.md, tasks.md, and verification.md from vault templates.

How do I check spec coverage before writing code?

Run /spec check <feature-id> after filling the proposal and drafting tasks.md. It maps each acceptance criterion to implementation tasks, reporting uncovered criteria as blockers and orphan tasks as warnings, without modifying any files.

Can I archive a spec without an adversarial review?

Archive refuses without a review.md containing a PASS or PASS-WITH-GAPS verdict matching the spec. The only escapes are a declared review: waived with a reason in proposal.md frontmatter, or the --force-without-review flag.

When should I skip Spec-Driven Development?

Skip SDD for trivial changes such as typos, comment-only edits, mechanical renames, doc-only changes, or obvious bugfixes under 20 LOC. Strategic planning across milestones belongs in a planning skill, and pure exploration needs no spec.

Does the spec skill work on Windows?

Yes, it is cross-platform. On Windows the agent reads the skill via AGENTS.md indirection and invokes the dotf spec CLI for mechanical operations, while Linux and macOS use POSIX commands through the Bash tool.

What happens if my spec still has AGENT-DRAFT tags at archive time?

Archive refuses to proceed if any [AGENT-DRAFT] or [AGENT-SUGGESTION] tags remain in proposal.md, tasks.md, or verification.md. You must accept, edit, or delete the tagged content first, or override with --force-with-drafts.