Skip to content

oliver-kriska/claude-elixir-phoenix / targets/dsh/skills/phx-full

phx-full

Verified

Run a portable sequential plan-work-verify-review-compound lifecycle. Use optional generic workers only when the runtime supports them.

references/execution-steps.md

View on GitHub
# Full Cycle Execution Steps

Use portable plan/work/verify/review instructions sequentially. Never transitively
invoke compound. Append one event per transition or outcome to `progress.md`; it
is the sole append-only state authority. Every event records monotonic `seq`,
`phase_visit`, `phase`, `cycle`, `task`, `task_attempt`, cumulative `blockers`,
`outcome`, and an `evidence` or `artifact` path. Task selection is legal only in
WORKING.

Discovery proposes depth and waits for the user gate. Planning writes and presents
the plan. Work updates checkboxes and append-only progress evidence. Verification
records exact commands and outcomes. Review is read-only; approved findings return
to WORKING as plan tasks. After accepted review, COMPOUNDING writes a solution
artifact only for a non-obvious reusable learning; otherwise it records SKIPPED.
The only successful order is REVIEWING → COMPOUNDING → COMPLETED.

Never silently continue through a blocker or limit. Report COMPLETE, BLOCKED, or
INCOMPLETE with cycle/retry counts, changed files, verification, review disposition,
artifacts, and the runtime-native resume action.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall