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/MODE-A-CHART.md

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

# Mode A — Chart the map

Invoked with `chart <loose idea>`. Requires orc-wayfinder/MAP.

> **🛑 Tracker writes**
>
> Steps 7–10 create the map and tickets on the tracker. The preview gate in steps 5–6 precedes them.

## Name the destination

1. Run `orc-grilling` + `orc-domain-modeling` to pin down the destination.

NOTE: the destination fixes the scope, so settle it first.

## Map the frontier

2. Grill again, breadth-first, fanning out across the whole space.
3. Surface the open decisions and the first takeable steps.
4. If this surfaces no fog, print the no-map gate and ask (options below).

No-map gate: the way is already clear and the journey fits one session. Print the headline per `orc-callouts`, then `the available user-question tool (or ask in chat)`.

```markdown
> **⛔ Gate — no map needed**
```

Options: hand off to `$orc-plan`; slice via `orc-to-issues`; chart anyway.

## Preview

5. Print `**📋 Preview — map + tickets**` with the payload below.
6. Ask with `the available user-question tool (or ask in chat)` to confirm before creating anything on the tracker.

Preview payload: the map body; every ticket title, type and question; the blocking edges.

## Create

7. Create the map per the tracker doc's wayfinding operations.
8. Create the specifiable tickets as children of the map.
9. Wire the blocking edges in a second pass, with real ids.
10. Write the cross-references in that same pass, with real ids.
11. Leave everything not yet specifiable in the fog section.

NOTE: items need ids before they can reference each other, hence the second pass. A placeholder `#<n>` auto-links to an unrelated issue.

## Fire the research subagents

12. For each research ticket, dispatch `orc-research` in the background.
13. Capture findings on a throwaway `research/<name>` branch linked from the ticket.
14. Push the branch.

NOTE: research tickets resolve in parallel. Open no PR for the research branch; nothing ever merges it.

## Stop

15. Stop. Charting is one session's work; it hand-resolves nothing.
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