planlisted

# Scalpel Plan Evaluate existing `.plan` files and identify gaps. This skill does not implement anything. ## Steps ### 1. Determine the Objective Check whether `$ARGUMENTS` was provided. | Arguments | Result | |-----------|--------| | provided | Arguments are the objective. Evaluate plans against them. | | absent | No objective. Check existing plans for standards alignment only; skip alignment and gap detection. | ### 2. Load Project Standards Look for standards and architecture documentation in this order and read every file found: 1. `AGENTS.md` 2. `CLAUDE.md` 3. `docs/ARCHITECTURE.md`, `docs/architecture.md`, or any file matching `docs/arch*` These files define the project's conventions, patterns, and constraints. If none exist, note that no standards were found and proceed without them. Do not invent standards. Do not apply conventions from outside these files. Only enforce what is explicitly documented. ### 3. Gather and Normalize Plan Files ```bash find . -name "*.plan" -not -path '*/.git/*' -not -path '*/node_modules/*' | sort ``` Read every plan file found. Before evaluating, normalize each one silently to the expected format: **Expected format:** ```markdown --- file: <path to target file> type: <add | modify | move | delete> --- ## Change <description> ``` **Normalization rules — apply automatically, no prompt:** - If the frontmatter is missing entirely, wrap the full file content in a `## Change` section and infer `file` from the plan's own pa