prp-task-create

A command that turns a focused code change into a detailed task list, including affected files, dependencies, tests, and rollback steps. It uses a PRP, a written implementation plan for a coding agent.

In plain words
What is it for?
Use it to plan a feature, bug fix, or refactor; research existing code patterns; define acceptance checks; and sequence implementation and validation tasks.
Why use it?
It reduces missed files, unclear requirements, and late discovery of side effects by organizing the work before coding begins.

Command for Claude Code

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/mort-lab/excel-mcp/prp-task-create
Clone the repo
git clone --depth 1 https://github.com/mort-lab/excel-mcp

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 516 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00516
Opus 5 $0.00000 $0.00258
Sonnet 5 $0.00000 $0.00103
Haiku 4.5 $0.00000 $0.00052

Measured 2d ago against content hash 56de31c18749, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

prp-task-create 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 2d 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.

Origin

This is a copy

100% identical to prp-task-create — 216 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/prp-commands/prp-task-create.md · 109 lines

How it starts

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

Create TASK PRP (Advanced)

Generate a comprehensive task list for focused changes with validation.

Task: $ARGUMENTS

Analysis Process

  1. Scope Definition

    • Identify all affected files
    • Map dependencies
    • Check for side effects
    • Note test coverage
  2. Pattern Research

    • Find similar changes in history
    • Identify conventions to follow
    • Check for helper functions
    • Review test patterns
  3. User Clarification

    • Confirm change scope
    • Verify acceptance criteria
    • Check deployment considerations
    • Identify blockers

PRP Generation

READ Using TASK_PRP/PRPs/prp_task.md format:

Context Section

context:
  docs:
    - url: [API documentation]
      focus: [specific methods]

  patterns:
    - file: existing/example.py
      copy: [pattern to follow]

  gotchas:
    - issue: "Library requires X"
      fix: "Always do Y first"

Task Structure

ACTION path/to/file:
  - OPERATION: [specific change]
  - VALIDATE: [test command]
  - IF_FAIL: [debug strategy]
  - ROLLBACK: [undo approach]

Task Sequencing

  1. Setup Tasks: Prerequisites
  2. Core Changes: Main modifications
  3. Integration: Connect components
  4. Validation: Comprehensive tests
  5. Cleanup: Remove temp code

Validation Strategy

  • Unit test after each change
  • Integration test after groups
  • Performance check if relevant
  • Security scan for sensitive areas

User Interaction Points

  1. Task Review

    • Confirm task breakdown
    • Validate sequencing
    • Check completeness
  2. Risk Assessment

    • Review potential impacts
    • Confirm rollback approach
    • Set success criteria

Critical Elements

  • Include debug patterns
  • Add performance checks
  • Note security concerns
  • Document assumptions

Output

Save as: TASK_PRP/PRPs/{task-name}.md

Quality Checklist

  • All changes identified
  • Dependencies mapped
  • Each task has validation
  • Rollback steps included
  • Debug strategies provided
  • Performance impact noted
  • Security checked
  • No missing edge cases

Read the full file on GitHub · 109 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.

  1. 2d ago First seen · 109 lines · 0 tokens per session scan A 56de31c18749

Subscribe to this mod's changes

prp-task-create is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 516 tokens. A static security scan graded it A with 0 findings. It is 100% identical to prp-task-create, differing in 216 lines, and is treated as a copy.