ss-planlisted

# Build Execution Plan Decompose a requirement or technical proposal into an executable, task-level implementation plan. Each task must be small enough for a single agent to complete independently, with explicit dependencies, exact file paths, and verification criteria. **Language of the plan:** write the plan's prose in the same language as the input document (or the project's existing docs, if that's a clearer signal); default to English when neither gives a signal. Code, commands, and file paths always stay in their original form regardless of prose language. **Zero-context assumption:** write the plan as if the executor has zero knowledge of the codebase and limited design taste. Every task must be fully self-contained — the executor should never need to "figure out" what to do. If a step changes code, show the code. If a step runs a command, show the command and its expected output. ## Inputs One of: - A link to a requirement or proposal document that your document-reading tool can fetch. - A local Markdown file path. - Plain text describing the requirement directly. If the input is missing or too thin to extract a goal, scope, and acceptance criteria, ask the user rather than guessing. ## Iron Rules **Violating any of these means stop and start over:** 1. **Comprehend before planning** — do not start decomposing until the entire input is read and understood. Skipping this voids the plan. 2. **Never guess** — if the input is ambiguous or missing information, ask