القائمة
Use when a task has written repo truth and implementation should proceed step by step with evidence.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when any oasis7 user request starts and must bind the canonical worktree, GitHub-backed task truth, and owner before routing.
Use when a branch is about to create a PR and needs fresh involved-role review.
Use when implementation is verified and the branch must proceed through review, PR, merge, and cleanup.
Use when about to claim a task is complete, tests passed, a branch is ready for PR, or a PR is ready to merge. Requires fresh verification, direct output inspection, and use of `./scripts/pm/claim-ready.sh` when the claim can be mapped to one verification command.
Use when a bound oasis7 task needs the next repo-owned workflow phase selected.
Use when assessing or developing the blocked production-supervisor target for a bound oasis7 task spanning multiple lifecycle phases.
| name | executing-project-tasks |
| description | Use when a task has written repo truth and implementation should proceed step by step with evidence. |
Canonical lifecycle: state machine, states, gates.
Use when the task already has written scope in prd.md, project.md, a handoff, or GitHub-backed task truth. Do not use for unresolved direction, observed unexplained failures, or finishing.
prd.md / project.md / GitHub-backed task truth../scripts/pm/bounded-command-output.py; inspect the bounded summary and retain the reported full artifact/digest for debugging.finishing-a-development-branch.If any command, test, or behavior is unexpected, automatically route to systematic-debugging, resolve the root cause, and resume the same step. Pause only for canonical external_wait or capability_blocked, recording resume authority and instruction from the canonical state contract.
Use ./scripts/pm/append-execution-log.sh when a durable local execution ledger is required. Module verification does not imply integration or release readiness.
Preserve declared write scopes and task truth; do not claim broader readiness than the evidence tier.
Large unverified batches; parallel planning truth; continuing after unexplained failures; treating module checks as release proof.