Skip to content

oliver-kriska/claude-elixir-phoenix / targets/pi/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/example-run.md

View on GitHub
# Example Full Cycle

The runtime discovers relevant context, proposes planning depth, and waits at the
user gate. After approval it creates the plan, presents it, executes approved
tasks in order, and records focused checks. It then runs the final verification
gate and a read-only review. Approved findings become plan tasks and consume a
bounded cycle. The ledger records PHASE_ENTER/PASS/FAIL and all counters. Only a
passing verification and accepted review advance REVIEWING → COMPOUNDING →
COMPLETED; limits or unresolved blockers return INCOMPLETE/BLOCKED.
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