agentmods.dev

agentic-development-starter-kit: Command for Claude Code

.cursor/commands/draft-spec.md

draft-spec is a command for Claude Code, Cursor from rhyanvargas/agentic-development-starter-kit. It costs 0 tokens per session (357 once invoked), scanned A, original, Apache-2.0.

A command for turning a feature idea or substantial bug report into a written software specification. The specification describes requirements, success conditions, assumptions, and how the work should be tested.

In plain words
What is it for?
It is for scanning related code, defining testable requirements, choosing a suitable feature or bug-fix format, and saving the specification in the project’s expected location.
Why use it?
It reduces ambiguity before coding and makes it easier to agree on what must change and how to verify it.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md).

This is rhyanvargas/agentic-development-starter-kit's own configuration. It tells Claude Code and Cursor how to work on agentic-development-starter-kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentic-development-starter-kit configures →

not rated 2repo 4d ago A scan 0 tokens original Apache-2.0
View source ↗ rhyanvargas/agentic-development-starter-kit
Reuse

Borrowing it

Nothing to install: this file belongs to rhyanvargas/agentic-development-starter-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rhyanvargas/agentic-development-starter-kit/main/.cursor/commands/draft-spec.md
Clone the repo
git clone --depth 1 https://github.com/rhyanvargas/agentic-development-starter-kit

Made for: Claude Code, Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for draft-spec

README.md
[![agentmods](https://agentmods.dev/badge/commands/rhyanvargas/agentic-development-starter-kit/draft-spec/github.svg)](https://agentmods.dev/commands/rhyanvargas/agentic-development-starter-kit/draft-spec)
Your own site
<a href="https://agentmods.dev/commands/rhyanvargas/agentic-development-starter-kit/draft-spec"><img src="https://agentmods.dev/badge/commands/rhyanvargas/agentic-development-starter-kit/draft-spec/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for draft-spec

Your own site · 80×15
<a href="https://agentmods.dev/commands/rhyanvargas/agentic-development-starter-kit/draft-spec"><img src="https://agentmods.dev/badge/commands/rhyanvargas/agentic-development-starter-kit/draft-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 357 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00357
Opus 5.5 $0.00000 $0.00143
Sonnet 5.5 $0.00000 $0.00071
Haiku 4.5 $0.00000 $0.00036

Measured 2mo ago against content hash 7808f7fe404a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

draft-spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/commands/draft-spec.md · 26 lines

What it actually says

/draft-spec

Generate a specification from a feature idea (or a surgical bugfix).

Skill

Read and follow skills/spec-driven-workflow (especially references/spec-writing-guide.md and references/artifact-homes.md). For Cursor output homes, also follow references/cursor-adapter.md. For non-trivial bugs, follow references/bugfix-workflow.md.

Usage

/draft-spec "your feature idea or description"
/draft-spec "Bug: …"   # use bugfix template when appropriate

Behavior

  1. If the idea is vague: surface assumptions and reframe into success criteria (2–3 questions max). Do not silently invent requirements.
  2. Choose entry mode: Requirements-First (default), Design-First when TECH/NFRs dominate, or Bugfix (Current / Expected / Unchanged) for non-trivial defects.
  3. Scan the codebase for related patterns.
  4. Write a testable spec (prefer REQ-XXX IDs + acceptance criteria + test strategy). Include Assumptions / Open Questions when anything is unresolved.
  5. Resolve the spec path via the skill (artifact-homes.md). As a Cursor / command, default to .cursor/docs/specs/{feature-name}.md unless the project already uses docs/specs/ or the user passed --out.
  6. Pause for user review on medium+ work; then suggest a cross-requirement analyze pass (references/analyze-requirements.md) before /plan-impl, or /implement-spec for small changes.

Do not duplicate the full playbook here — the skill is the source of truth.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 26 lines · 0 tokens per session scan A 7808f7fe404a

Subscribe to this mod's changes

draft-spec is a command published in the GitHub repository rhyanvargas/agentic-development-starter-kit (2 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 357 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

PlanningWriting and docs
Related

draft-spec compared with commands from other repositories

draft-spec next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
draft-specrhyanvargas/agentic-development-starter-kitCommand24d agoApache-2.0A0Claude Code, Cursor
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code