What is OpenSpec: Proposal?

A command for planning a proposed change in an OpenSpec project, a system that records software changes in design documents before coding starts.

It reviews the project context, creates proposal, task, and design files, records specification changes, and asks questions about missing details.

It keeps proposals separate from implementation and checks them against the project's existing specifications, reducing unclear or unapproved changes.

OpenSpec: Proposal — Command by fenwei-dev

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/fenwei-dev/mcp2skill/proposal

Clone the repo

git clone --depth 1 https://github.com/fenwei-dev/mcp2skill

Made for: Claude Code.

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 557 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00557
Opus 5	$0.00000	$0.00279
Sonnet 5	$0.00000	$0.00111
Haiku 4.5	$0.00000	$0.00056

Measured yesterday against content hash 5110717559f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

OpenSpec: Proposal 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 yesterday.

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.

Origin

This is a copy

100% identical to OpenSpec: Proposal — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/openspec/proposal.md · 29 lines

What it actually says

name: OpenSpec: Proposal description: Scaffold a new OpenSpec change and validate strictly. category: OpenSpec tags: [openspec, change]

Guardrails

Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
Keep changes tightly scoped to the requested outcome.
Refer to openspec/AGENTS.md (located inside the openspec/ directory—run ls openspec or openspec update if you don't see it) if you need additional OpenSpec conventions or clarifications.
Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.

Steps

Review openspec/project.md, run openspec list and openspec list --specs, and inspect related code or docs (e.g., via rg/ls) to ground the proposal in current behaviour; note any gaps that require clarification.
Choose a unique verb-led change-id and scaffold proposal.md, tasks.md, and design.md (when needed) under openspec/changes/<id>/.
Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
Capture architectural reasoning in design.md when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
Draft spec deltas in changes/<id>/specs/<capability>/spec.md (one folder per capability) using ## ADDED|MODIFIED|REMOVED Requirements with at least one #### Scenario: per requirement and cross-reference related capabilities when relevant.
Draft tasks.md as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
Validate with openspec validate <id> --strict and resolve every issue before sharing the proposal.

Reference

Use openspec show <id> --json --deltas-only or openspec show <spec> --type spec to inspect details when validation fails.
Search existing requirements with rg -n "Requirement:|Scenario:" openspec/specs before writing new ones.
Explore the codebase with rg <keyword>, ls, or direct file reads so proposals align with current implementation realities.

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.

yesterday First seen · 29 lines · 0 tokens per session scan A 5110717559f8

Subscribe to this mod's changes

OpenSpec: Proposal is a command published in the GitHub repository fenwei-dev/mcp2skill (55 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 557 tokens. A static security scan graded it A with 0 findings. It is 100% identical to OpenSpec: Proposal, differing in 0 lines, and is treated as a copy.

OpenSpec Planning [openspec, change]