manual

A command that loads and checks a product requirements document (PRD), a file describing a project's goals, work items, priorities, dependencies, and conditions for completion.

In plain words
What is it for?
Use it to open an existing PRD, validate its stories and acceptance criteria, copy it into the working folder when needed, and start review mode.
Why use it?
It catches missing or invalid requirements before work begins and prepares the files needed to track review findings.

Command

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/taoidle/plan-cascade/manual
Clone the repo
git clone --depth 1 https://github.com/Taoidle/plan-cascade
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 738 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.00025 $0.00738
Opus 5 $0.00013 $0.00369
Sonnet 5 $0.00005 $0.00148
Haiku 4.5 $0.00003 $0.00074

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

Security

Grade A, and why

manual 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 hybrid-manual — 6 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.

skills/hybrid-ralph/commands/manual.md · 154 lines

How it starts

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

Hybrid Ralph - Load Manual PRD

You are loading an existing Product Requirements Document (PRD) from a file.

Step 1: Parse PRD Path

Get the PRD path from arguments:

PRD_PATH="{{args|first arg or 'prd.json'}}"

Step 2: Verify PRD Exists

if [ ! -f "$PRD_PATH" ]; then
    echo "ERROR: PRD file not found: $PRD_PATH"
    echo "Please provide a valid path to a prd.json file"
    exit 1
fi

Step 3: Read and Validate PRD

Read the PRD file and validate structure:

Required fields:

  • metadata.description
  • goal
  • stories array

Each story must have:

  • id
  • title
  • description
  • priority (high/medium/low)
  • dependencies (array of story IDs)
  • acceptance_criteria (array)

If validation fails, show specific errors and suggest fixes.

Step 4: Copy PRD to Current Directory (if needed)

If the PRD is not already prd.json in the current directory:

if [ "$PRD_PATH" != "prd.json" ]; then
    cp "$PRD_PATH" prd.json
    echo "Copied PRD to prd.json"
fi

Step 5: Initialize Supporting Files (if missing)

Create findings.md if it doesn't exist:

if [ ! -f "findings.md" ]; then
    cat > findings.md << 'EOF'
# Findings

Research and discovery notes will be accumulated here.

Use <!-- @tags: story-id --> to tag sections for specific stories.
EOF
fi

Create progress.txt if it doesn't exist:

if [ ! -f "progress.txt" ]; then
    cat > progress.txt << 'EOF'
# Progress Log

Story execution progress will be tracked here.
EOF
fi

Step 6: Display PRD Review

Show a comprehensive PRD review:

============================================================
PRD REVIEW
============================================================

## Goal

{goal from PRD}

## Objectives

- {objective 1}
- {objective 2}
...

## Stories Summary

Total Stories: {count}
By Priority:
  High: {count}
  Medium: {count}
  Low: {count}

## All Stories

### story-001: {title} [High]
Description: {description}
Dependencies: {none or list}
Acceptance Criteria:
  - {criterion 1}
  - {criterion 2}
...

### story-002: {title} [Medium]
...

## Execution Batches

Batch 1 (parallel):
  - story-001
  - story-002

Batch 2:
  - story-003 (depends on: story-001)

...

============================================================

Read the full file on GitHub · 154 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 · 154 lines · 25 tokens per session scan A 653a3bbb45ee

Subscribe to this mod's changes

manual is a command published in the GitHub repository Taoidle/plan-cascade (131 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 738 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to hybrid-manual, differing in 6 lines, and is treated as a copy.