Skip to content

HigorAlves/orc / codex/orc/content/skills/phases

phases

Verified

Per-phase playbooks for orc commands, loaded one phase at a time

FileKindSize
SKILL.mdskill md3.4 KB
references/flow/PHASE-2-RFC.mdmarkdown606 B
references/flow/PHASE-3-PLAN.mdmarkdown1.4 KB
references/flow/PHASE-4-START.mdmarkdown3.0 KB
references/flow/PHASE-5-IMPLEMENT.mdmarkdown6.6 KB
references/flow/PHASE-6-QA.mdmarkdown3.5 KB
references/flow/PHASE-7-SHIP.mdmarkdown3.1 KB
references/flow/PHASE-8-ADDRESS.mdmarkdown921 B
references/flow/PHASE-9-CLEANUP.mdmarkdown1.9 KB
references/plan/DISCOVERY.mdmarkdown871 B
references/plan/PHASE-1-INIT.mdmarkdown2.1 KB
references/plan/PHASE-2-DRAFT.mdmarkdown2.5 KB
references/plan/PHASE-3-GRILL.mdmarkdown333 B
references/plan/PHASE-4-CONFIRM.mdmarkdown1.5 KB
references/plan/PHASE-5-DECOMPOSE.mdmarkdown443 B
references/plan/PRD.mdmarkdown1.1 KB
references/plan/REFACTOR.mdmarkdown1.1 KB
references/qa/PACKET.mdmarkdown2.7 KB
references/qa/PHASE-2-VERIFY.mdmarkdown662 B
references/qa/PHASE-3-REVIEW.mdmarkdown939 B
references/qa/PHASE-4-BROWSER.mdmarkdown915 B
references/qa/PHASE-5-VERDICT.mdmarkdown1.8 KB
references/qa/PHASE-6-PUBLISH.mdmarkdown760 B
references/retro/PHASE-1-SOURCES.mdmarkdown1.2 KB
references/retro/PHASE-2-CANDIDATES.mdmarkdown4.8 KB
references/retro/PHASE-3-PRESENT.mdmarkdown892 B
references/retro/PHASE-4-ACT.mdmarkdown1.2 KB
references/retro/PHASE-5-PROPOSE.mdmarkdown2.1 KB
references/ship/PHASE-1-VERIFY.mdmarkdown733 B
references/ship/PHASE-2-REVIEW.mdmarkdown369 B
references/ship/PHASE-3-COMPOSE.mdmarkdown2.0 KB
references/ship/PHASE-4-GATE.mdmarkdown1.5 KB
references/ship/PHASE-4.5-SIZE-GATE.mdmarkdown2.9 KB
references/ship/PHASE-5-PUSH.mdmarkdown2.9 KB
references/ship/PHASE-6-CLEANUP-HINT.mdmarkdown794 B
references/stack-pr/PHASE-1-TOOLING.mdmarkdown1001 B
references/stack-pr/PHASE-2-PRECONDITIONS.mdmarkdown916 B
references/stack-pr/PHASE-3-ANALYZE.mdmarkdown1.0 KB
references/stack-pr/PHASE-4-PREVIEW.mdmarkdown2.1 KB
references/stack-pr/PHASE-5-EXECUTE.mdmarkdown1.9 KB
references/stack-pr/PHASE-6-WRITEBACK.mdmarkdown1.6 KB
references/stack-pr/PHASE-7-SUMMARY.mdmarkdown681 B
references/stack-pr/SMART.mdmarkdown877 B
references/triage/BRIEFS.mdmarkdown1.8 KB
references/triage/OUT-OF-SCOPE.mdmarkdown1.3 KB
references/triage/PHASE-1-QUEUE.mdmarkdown786 B
references/triage/PHASE-2-ITEM.mdmarkdown2.4 KB
references/triage/PHASE-3-OVERRIDE.mdmarkdown610 B
references/triage/PHASE-4-INTAKE.mdmarkdown2.0 KB
references/triage/ROLES.mdmarkdown1.2 KB
references/triage/VALIDITY.mdmarkdown2.2 KB
references/wayfinder/MAP.mdmarkdown4.6 KB
references/wayfinder/MODE-A-CHART.mdmarkdown2.1 KB
references/wayfinder/MODE-B-WORK.mdmarkdown1.7 KB

references/qa/PHASE-5-VERDICT.md

View on GitHub
<!-- orc-qa/P5 -->
_Loaded on demand via orc-phases. Do not run this phase from memory — this file is the phase._

# Phase 5 — Write the verdict

1. In web mode, Read `orc-qa/PACKET` and check every required artifact exists.
2. If a required artifact is missing, print the Blocked callout from `orc-qa/PACKET` and stop.
3. Write `qa-verdict.json` at the path below, shape per `orc-state-protocol` `references/schema.md`.
4. Add one `checks[]` row per suite check, per slice acceptance criterion, per browser walk.
5. Copy the acceptance rows from the packet's `qa-manifest.json` `acceptance[]`; never re-derive them from prose.
6. Mark an un-scoreable criterion `result: "skipped"` with the manifest's `note`, visibly.
7. If the manifest is missing or a criterion lacks a result, record incomplete evidence.
8. Compute the `verdict` with the rule below.
9. Stamp `headSha` and `generatedAt`.
10. Append the QA block below to `.orc/<branch>/files/progress.md`.
11. Run `orc-state phase set <n> --label qa-complete`, then `orc-state digest write -`.

Verdict path: `${ORC_STATE_DIR}/<sanitized-branch>/files/qa-verdict.json`.

Acceptance row shape: `kind: "acceptance"`; `evidence` is the manifest row's first `evidence` entry. Suite checks: tests, lint, type-check.

Verdict rule (mechanical; agents never decide it; ship and flow gates read this file):

```
any check fail     → fail
else any partial   → partial
else               → pass
```

Progress block:

```
## QA — <ISO-timestamp>
- Tests: pass/fail
- Lint: pass/fail
- Type-check: pass/fail
- Self-review findings: <count>
- Env: <ready (reused) | ready (booted <N>s) | fallback (host) | skipped>
- Browser QA: <pass|fail|partial|skipped (code-only)>
- Artifact dir: .orc/<branch>/files/qa/  (if web mode)
```

NOTE: incomplete evidence is never a pass. The state calls follow `orc-state-protocol`.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall