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/cycle-patterns.md

View on GitHub
# Cycle Patterns

A cycle is one WORKING → VERIFYING → REVIEWING pass. Increment `task_attempt`
immediately before each attempt and increment `cycle` immediately before
VERIFYING. Count a cumulative blocker once, when its task first becomes blocked.
Reject a transition before its bound would be exceeded: `--max-retries N` permits
the initial attempt plus N retries. Review is read-only; findings return WORKING.
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