Plan Out

    2

    A Claude skill that plans big features as small, non-contradicting spec modules with a decision log, and cleans up docs that have drifted out of sync.

    $20

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    5.0 (1 review)

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    plan-out

    Example session with this skill installed

    Let's plan the new user notification system. We need to support email and push. Specify the modules and the first few decisions.

    • Read your context and instructions
    • Compiled the plan-out

    I have initialized the planning structure for the Notification System. I've created the core modules and logged the initial architectural decisions regarding transport types and provider selection.

    Notification System Plan

    Decisions Log (docs/decisions.md)

    IDDecisionOwnerStatus
    D001Support Email and Push as primary transportsmodules/transportsactive
    D002Use a unified provider interface for notification deliverymodules/engineactive

    Proposed Modules

    • docs/modules/engine.md: Logic for routing notifications based on user preferences.
    • docs/modules/transports.md: Schema for email and push payloads.
    • docs/modules/preferences.md: User-level opt-in/out state management.

    Initial Task List (docs/tasks/notification-mvp.md)

    
    # Task: Notification MVP
    - [ ] Define notification payload schema in `modules/transports` [implements: transports#schema]
    - [ ] Create abstract provider interface in `modules/engine` [implements: engine#interface]
    - [ ] Log default retry policy in `decisions.md`
    

    Consistency Check Result

    • python scripts/check.py check --docs docs
    • Result: PASS (3 modules created, 2 decisions active, 0 contradictions).

    Next steps

    1. Review the transports module to confirm payload fields for Push notifications.
    2. Decide on the specific third-party provider for Email (SendGrid vs SES) so I can log D003.
    3. Approve the task list to begin implementation.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    plan-out

    A skill for Claude that plans big features as small, scoped spec modules, keeps them consistent as plans change, and cleans up docs folders that have drifted into contradiction.

    The problem

    Plan a feature over several AI sessions and you end up with a pile of files that are each internally consistent but disagree with each other. Session 3 changes a decision from session 1, nothing updates session 1's file, and both claim to be true. Asking an AI to reconcile them makes it worse: it can't tell the current decision from a superseded one, so it guesses, blends, and invents.

    How plan-out prevents it

    • One owner per fact. Every fact lives in exactly one module; everything else links to it.
    • A decision log with status. Each decision has an id, an owner, and a status of active or superseded. Changes supersede, never overwrite.
    • Specs and tasks stay separate. Modules are the lasting documentation. Tasks are derived from them, link back one-way, and are archived when done.
    • A script is the referee. check.py mechanically catches broken links, stale decision references, duplicate definitions, uncovered sections and more, so consistency does not depend on an AI's impression.
    • Never assume. Unknowns become batched questions with recommended answers. Skipped questions are logged as explicit defaults.
    • Cleanup is extractive. Existing docs are moved verbatim into the new structure, conflicts are decided by you, and a ledger proves nothing was lost or invented.

    What it does

    You sayIt does
    "Plan a feature that lets users upload files" (vague or detailed)Plays back its understanding, asks clarifying questions in small batches, proposes modules for approval, then writes modules, a decision log and a task list
    "Change the upload limit to 25 MB"Finds the owning module, shows the impact, supersedes the old decision, edits only what must change, flags affected tasks
    "Our docs contradict each other, clean them up"Inventories, extracts claims, shows you each conflict, migrates verbatim on a git branch, verifies with a ledger, then deletes the old files

    The result is docs a new engineer can learn the codebase from, plus a task list an AI agent can implement without asking anyone anything.

    Output layout

    docs/
      README.md        generated index
      modules/         one file per module (the lasting spec)
      decisions.md     decision log
      tasks/           active task lists
        archive/       finished work, frozen
    

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires Python to run the check script. Documentation must follow specific templates in the docs/ folder to maintain consistency.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    5.0
    1 review
    5
    1
    4
    0
    3
    0
    2
    0
    1
    0

    Trust & safety

    Security scan

    Security scan passed 18 days ago

    Software
    PythonGit

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed18 days ago
    Updated16 days ago

    What's inside

    Frequently Asked Questions

    'Plan Out' uses a modular system where every requirement has a single owner, combined with a Python-based check script that programmatically flags contradictions and broken links across your files.

    This skill is framework-agnostic and works with any AI agent capable of file manipulation and local script execution, provided a standard Python environment is available to run the validation script.

    You receive a suite of standardized markdown templates for modules and decision ledgers, a custom Python validation script (`check.py`), and the logic for the agent to execute structured planning workflows.

    The skill includes a dedicated decision ledger workflow that marks old choices as superseded while preserving them in history, ensuring your current specs reflect the latest architecture without losing context.

    While the skill works with any project, it requires your documentation to follow a specific directory structure and template format so the automated logic checker can accurately parse and validate your plans.

    Unlike standard prompting, which often leads to 'hallucinated' requirements during rewrites, this skill uses surgical editing and a programmatic arbiter to ensure every change is logically sound and linked to a verified source.

    New in Agents & Orchestration