pwf-work

Execute Unplanned Work (Fast Path)

Use this command for small fixes, minor adjustments, and focused tasks outside formal plans. For phase execution from docs/plans/, use /pwf-work-plan. Apply skills/using-psters-workflow/SKILL.md at start.

Documentation Intent (Read This First)

Documentation in docs/ is operational memory for future AI and engineers, not a release note.

Every documentation update must help a future implementation answer quickly:

• Where is the source of truth?
• What is implemented now vs only planned?
• Which invariants/rules cannot be broken?
• Which files/methods must change together?
• What are the known gotchas and safe change steps?

Avoid generic text that could apply to any project.

⛔ MANDATORY WORKFLOW — NEVER SKIP ANY STEP

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

---

Input

<work_description> #$ARGUMENTS </work_description>

If empty, ask: "What would you like me to work on?"

---

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

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

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

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

1. If the description is vague, ask one or two clarifying questions first.

2. Classify scope first (trivial vs non-trivial):

   • Trivial: <=2 files, no entities/migrations/endpoints/auth model changes.
   • If trivial, use lightweight path:
     • read only docs/solutions/patterns/critical-patterns.md (if exists) and directly relevant doc,
     • skip mandatory research-agent spawning,
     • keep focused implementation + verification evidence.
   • If non-trivial, follow full workflow below.

3. Load docs baseline via skill (REQUIRED):

   • Apply skills/docs-baseline-loading/SKILL.md.
   • Read mandatory baseline docs before implementation.
   • Create any missing canonical baseline docs immediately using the skill's required minimum sections.
   • Then read scope-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)
   • Search docs/solutions/ by feature keywords for known gotchas.
   • If any other expected doc file is missing: create it immediately with a useful baseline (not placeholders). Minimum sections:
     • Purpose (business scope)
     • Source of Truth Files (exact paths)
     • Current Implementation Snapshot (what exists now)
     • Planned/Upcoming Contract (only if plan exists; clearly marked as planned)
     • Invariants and Gotchas
     • Safe Change Checklist for Future AI Work
     • Related Plan and Docs