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/ship/PHASE-5-PUSH.md

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

# Phase 5 โ€” Push + create PR

> **๐Ÿ›‘ Outward write**
>
> Steps 1โ€“2 push and open the PR. Step 4 posts a PR comment only after the `orc-evidence-publish` answer.

1. Run `git push -u origin <branch>`.
2. Run `gh pr create --title "<title>" --body "<body>" [--draft] [--base <base>]`.
3. Echo the PR URL.
4. If the QA manifest below exists, invoke `orc-evidence-publish` with the inputs below.
5. In workspace mode, run the two-pass loop below instead of steps 1โ€“3.

QA manifest: `${ORC_STATE_DIR}/<sanitized-branch>/files/qa/qa-manifest.json`. Inputs: `qaDir`, the packet's `verdict`, the new PR. Its PR-comment question (hard-outward, header `Post`) offers the verdict table and links on the PR just opened. Keep-local is the default; nothing posts without the answer.

## Workspace mode: two-pass loop

Pass 1 โ€” push + create per repo, sequential so `gh pr create` observes a clean push:

6. Skip any repo whose orc-ship/P4.5 produced a stack; its `linkedPRs[]` entries already exist.
7. For each remaining repo, push and create with the loop below.
8. Append each new PR to `linkedPRs` in `orc.json` (the `jq` in the loop).

```bash
for r in $targetRepos; do
  cd "$ORC_WORKSPACE_ROOT/$r"
  # If Phase 4.5 already opened a stack for this repo, skip โ€” entries are in linkedPRs already.
  already_stacked=$(jq -r --arg r "$r" --arg b "$BRANCH" \
    '.sessions[] | select(.branch == $b) | .linkedPRs | map(select(.repo == $r and .stackId != null)) | length' \
    "$ORC_STATE_DIR/orc.json")
  [ "${already_stacked:-0}" -gt 0 ] && continue

  branch=$(jq -r ".sessions[] | select(.branch == \"$BRANCH\") | .perRepoState.\"$r\".branch // \"$BRANCH\"" "$ORC_STATE_DIR/orc.json")
  git push -u origin "$branch"
  pr_url=$(gh pr create --title "<title>" --body "<body-without-cross-links-yet>" [--draft] [--base <base>])
  jq --arg r "$r" --arg url "$pr_url" \
     '(.sessions[] | select(.branch == "'"$BRANCH"'") | .linkedPRs) += [{repo: $r, url: $url, stackId: null, stackPosition: null, stackedOn: null}]' \
     "$ORC_STATE_DIR/orc.json" > tmp && mv tmp "$ORC_STATE_DIR/orc.json"
done
```

Pass 2 โ€” inject the reciprocal "Linked PRs" block, after all PRs exist:

9. For each PR, run `gh pr edit <url> --body "$(updated body)"` with the block appended.
10. Source the merge order from the plan's "Merge order" line; omit it if absent.
11. Echo all N PR URLs to the user.

Default (terse) template:

```
## Linked
api#311 (this) ยท ui#447
order: api โ†’ ui
```

`--verbose` template:

```
## Linked PRs

This PR is part of a workspace change spanning N repos:

- org/api#311 โ€” this PR
- org/ui#447 โ€” UI changes

Merge order: api โ†’ ui (per workspace plan).
```

NOTE: PR #1 does not know PR #2's number at creation time, hence the second pass. For a stacked repo, `gh pr create` would create a duplicate, hence step 6.
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