A command that turns a user's requirements into a written software implementation plan and saves it in a specifications folder. The plan covers the problem, technical design, build steps, risks, testing, and completion criteria.

Use it to plan a feature or fix, choose an architecture, identify likely problems, define tests, and document what success means.

It gives developers a shared blueprint before coding begins and records the decisions in a file that another developer can follow.

How vincenthopf/computer-use-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to vincenthopf/computer-use-mcp. 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/vincenthopf/computer-use-mcp/main/.claude/commands/quick-plan.md

Clone the repo

git clone --depth 1 https://github.com/vincenthopf/computer-use-mcp

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/vincenthopf/computer-use-mcp/quick-plan/github.svg)](https://agentmods.dev/commands/vincenthopf/computer-use-mcp/quick-plan)

Your own site

<a href="https://agentmods.dev/commands/vincenthopf/computer-use-mcp/quick-plan"><img src="https://agentmods.dev/badge/commands/vincenthopf/computer-use-mcp/quick-plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/vincenthopf/computer-use-mcp/quick-plan"><img src="https://agentmods.dev/badge/commands/vincenthopf/computer-use-mcp/quick-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 509 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.

Model	Per session	Once invoked
Fable 5.1	$0.00016	$0.00509
Opus 5.5	$0.00006	$0.00204
Sonnet 5.5	$0.00003	$0.00102
Haiku 4.5	$0.00002	$0.00051

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

Security

Grade A, and why

quick-plan 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.

.claude/commands/quick-plan.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Quick Plan

Create a detailed implementation plan based on the user's requirements provided through the USER_PROMPT variable. Analyze the request, think through the implementation approach, and save a comprehensive specification document to PLAN_OUTPUT_DIRECTORY/<name-of-plan>.md that can be used as a blueprint for actual development work.

Variables

USER_PROMPT: $ARGUMENTS PLAN_OUTPUT_DIRECTORY: specs/

Instructions

Carefully analyze the user's requirements provided in the USER_PROMPT variable
Think deeply (ultrathink) about the best approach to implement the requested functionality or solve the problem
Create a concise implementation plan that includes:
- Clear problem statement and objectives
- Technical approach and architecture decisions
- Step-by-step implementation guide
- Potential challenges and solutions
- Testing strategy
- Success criteria
Generate a descriptive, kebab-case filename based on the main topic of the plan
Save the complete implementation plan to PLAN_OUTPUT_DIRECTORY/<descriptive-name>.md
Ensure the plan is detailed enough that another developer could follow it to implement the solution
Include code examples or pseudo-code where appropriate to clarify complex concepts
Consider edge cases, error handling, and scalability concerns
Structure the document with clear sections and proper markdown formatting

Workflow

Analyze Requirements - THINK HARD and parse the USER_PROMPT to understand the core problem and desired outcome
Design Solution - Develop technical approach including architecture decisions and implementation strategy
Document Plan - Structure a comprehensive markdown document with problem statement, implementation steps, and testing approach
Generate Filename - Create a descriptive kebab-case filename based on the plan's main topic
Save & Report - Write the plan to PLAN_OUTPUT_DIRECTORY/<filename>.md and provide a summary of key components

Report

After creating and saving the implementation plan, provide a concise report with the following format:

Read the full file on GitHub · 56 lines

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.

2mo ago First seen · 56 lines · 16 tokens per session scan A af2b064853e7

Subscribe to this mod's changes

quick-plan is a command published in the GitHub repository vincenthopf/computer-use-mcp (0 stars, last pushed 22d ago), licensed MIT. It adds 16 tokens to every session and 509 once invoked, about $0.0001 per session on Opus 5.5. 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.

Planning

quick-plan next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
quick-planvincenthopf/computer-use-mcp	Command	0	22d ago	MIT	A	16	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
speckit.bug.testgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code

computer-use-mcp: Command for Claude Code