pwf-work-plan

Step 3 — Execute One Planned Phase

Use this command to execute one phase from docs/plans/ with full discipline: read docs first, implement, build, and update docs. Apply skills/using-psters-workflow/SKILL.md at start.

Documentation Intent (Read This First)

Docs updated during /pwf-work-plan must become reliable implementation memory for future phases and future AI runs.

Do not write generic summaries. Document:

• what is already implemented in code after this phase,
• what remains planned in later phases,
• where to edit safely next time,
• and which constraints must not be violated.

⛔ MANDATORY WORKFLOW — NEVER SKIP ANY STEP

You MUST execute steps 1 through 5 IN ORDER. Do NOT jump to implementation. Your FIRST action must be reading the plan file and documentation (Step 1), NOT editing code. If you skip Step 1 or Step 4, the workflow is BROKEN.

---

Input

<plan_input> #$ARGUMENTS </pwf-plan_input>

If empty or not pointing to a plan file, ask: "Which plan file? (e.g. docs/plans/20260312-feat-xyz-plan.md)"

---

Step 1: Load Context (BLOCKING — must complete before any code changes)

Your first tool calls MUST be Read calls. Do NOT start implementing.

Before Step 1 execution details, resolve extension guidance for before_work_plan:

• node ${CURSOR_PLUGIN_ROOT}/scripts/resolve-workflow-extensions.mjs before_work_plan

1. Read the plan file fully.

   • Validate task format in target phase:
     • - [ ] T### [P?] [USx?] Description with file path
   • If format is inconsistent, normalize the phase task list before execution (or ask user to run /pwf-plan refinement).

2. Identify the target phase — first ⬜ Pending phase, or the one specified by the user. If the argument names a phase number (e.g. "Phase 2"), start at that phase.

3. Load docs baseline via skill (REQUIRED):

   • Apply skills/docs-baseline-loading/SKILL.md.
   • Read mandatory baseline docs before implementation.
   • Create missing canonical baseline docs immediately using the skill's required minimum sections.
   • Then read phase-specific docs:
     • docs/solutions/patterns/critical-patterns.md (if exists)
     • docs/modules/<module>.md (backend scope)
     • docs/features/<feature>.md (frontend scope)
     • docs/lambdas/<repo>.md (Lambda scope)
     • docs/runbooks/README.md (operational/deploy scope)
     • relevant docs/solutions/ entries by feature keywords
   • If any other expected doc file is missing: create it immediately with a useful baseline. Minimum sections:
     • Purpose
     • Source of Truth Files
     • Current Implementation Snapshot
     • Phase Scope (Current Plan) with explicit planned markers
     • Invariants and Gotchas
     • Safe Change Checklist for Future AI Work
     • Related Plan and Docs