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/triage/VALIDITY.md

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

# Validity check

Five questions decide whether a report deserves work: is it real (steps 1–3), a duplicate (4), already done (5–6), in scope (7), detailed enough (8)? Step 9 adds a severity. `orc-triage/P2` and `orc-triage/P4` run every step.

> **⚠️ Caution**
>
> Investigate, never fix: no commits, no pushes, no tracker writes, no Sentry writes.

## Steps

1. Reproduce the bug from the reporter's steps, or run the named command.
2. For a stack trace, find each frame in the current code; list frames that no longer exist.
3. For a PR, check out the branch, run the relevant tests, then switch back.
4. Search open tracker items for a duplicate by domain concept, not the report's wording.
5. Run `git fetch origin`, then search `git log origin/main` for the fix or feature.
6. When the work exists on main, run `gh release list --limit 1` and check the release contains it.
7. Read `docs/agents/out-of-scope.md` per `orc-triage/OUT-OF-SCOPE`, and `SCOPE.md` when present.
8. List each fact the next person needs that the report does not give.
9. Assign `sev-1` (production broken now), `sev-2` (broken, workaround exists) or `sev-3`.

NOTE: match duplicates and out-of-scope entries by concept: "night theme" matches a Dark Mode entry.

## Verdict

| Verdict | When | Evidence to print |
|---|---|---|
| valid | real, new, not done, in scope, enough detail | the code path and the reproduction |
| duplicate | an open item covers the same concept | a link to the original |
| already done | main or a release carries the work | the commit, and the release when one carries it |
| out of scope | the KB or `SCOPE.md` rejects the concept | the entry |
| not reproduced | the steps run clean on current code | what ran, and its output |
| needs info | a fact from step 8 blocks the next person | the missing facts |

## Next command

Suggest one command with `**➡️ Next**`. Never start it.

| Condition | Suggest |
|---|---|
| `sev-1` at any verdict | `$orc-incident` |
| valid bug | `$orc-debug` |
| valid enhancement | `$orc-flow` |
| any other verdict | none |
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