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/wayfinder/MAP.md

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

# Map and ticket reference

Shared by orc-wayfinder/A and orc-wayfinder/B. Read it once per session, before the mode module.

## Principles

- **Plan, don't do.** Each ticket resolves a decision. The map is complete when nothing remains to decide before someone goes and does the thing. The pull to just do the work signals the edge of the map: time to hand off. A map's **Notes** can override this; absent that, produce decisions, not deliverables.
- **Refer by name.** Every map and ticket has a name: its title. In everything the human reads, use the name with the link riding inside (`[Pick the session store](url)`), never a bare `#42`. A wall of numbers is illegible.
- **One ticket per session.** Never resolve more than one ticket per session. Research tickets are the exception: they run as background subagents.

## The map

One tracker item labelled `wayfinder:map` (or the tracker doc's equivalent). It is the canonical artifact, loaded once per session at low resolution. It is an **index**, not a store: a decision lives in exactly one place, its ticket, and the map only gists and links it. Open tickets do not appear in the body; the tracker's frontier query finds them.

```markdown
## Destination

<what reaching the end looks like — the spec, decision, or change this effort
is finding its way to. One or two lines; every session orients to it first.>

## Notes

<domain; skills every session should consult; standing preferences>

## Decisions so far

- [<closed ticket title>](link) — <one-line gist of the answer>

## Not yet specified

<fog of war — see below>

## Out of scope

<work ruled beyond the destination — see below>
```

## Tickets

Each ticket is a child of the map. Its body is one question sized to a single fresh-context session:

```markdown
## Question

<the decision or investigation this ticket resolves>
```

- Each ticket carries one `wayfinder:<type>` label.
- `wayfinder:` labels are the only labels a map and its tickets carry. Never a triage label like `ready-for-agent`: tickets are decisions, not implementation work.
- A session **claims** a ticket by assigning it, before any work. The assignee IS the claim; open + unassigned = unclaimed.
- Blocking uses the tracker's **native** dependency relationship, so the frontier renders in the tracker's own UI. Fallback conventions per the tracker doc.
- A ticket is **unblocked** when every blocker has closed. The **frontier** is the open, unblocked, unclaimed children: the edge of the known.
- Record answers on resolution; never pre-write them into the body. Link assets; never paste them.

## Ticket types

Every ticket is **HITL** (worked live with a human) or **AFK** (agent-driven). In HITL the agent never stands in for the human's side; a grilling that answers its own questions has broken this.

- **Research** (AFK) — surface a fact a decision waits on, from docs, APIs or knowledge bases outside the working directory. Resolve via `orc-research` as a background subagent.
- **Prototype** (HITL) — raise the fidelity of the discussion with a cheap concrete artifact to react to, via `orc-prototype`. Link the artifact as an asset.
- **Grilling** (HITL) — conversation; the default type. Always `orc-grilling` + `orc-domain-modeling`.
- **Task** (HITL or AFK) — manual work that must happen before a decision is possible: sign up for the service, provision access, move the data so its shape is visible. The one type that *does* rather than decides; it earns its place by unblocking a decision, not by delivering the destination. AFK where the agent can drive; otherwise hand the human a precise checklist. The answer records what happened and the facts later tickets depend on.

## Fog of war

The map is *deliberately* incomplete: never chart what you cannot yet see. **Not yet specified** holds the dim view: decisions you can tell are coming but cannot pin down, because they hang on open questions. Resolving a ticket clears fog; what is now specifiable graduates into fresh tickets.

The test is whether you can state the question precisely **now**, not whether you can answer it:

- Sharp question → ticket, even if blocked.
- Fuzzy → fog, uncut. One patch can graduate into several tickets, or none.

## Out of scope

The destination fixes the scope. Work beyond it is not fog and never graduates. When an existing ticket turns out to sit past the destination, **close it** and leave one line in **Out of scope**: gist, why, link to the closed ticket. It stays out of Decisions-so-far, which records only the route walked.
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