← ClaudeAtlas

orientlisted

Use this skill for Shape Up step 7 (Orient) — the builder-led reconnaissance pass that runs AFTER kick-off and BEFORE any task board exists. Triggers on: "orient on this feature", "scout the codebase for this pitch", "where does this pitch touch the code", "do an orient pass", "recon before we plan", "spike the riskiest part before mapping scopes". The tech-lead orchestrator invokes it at step 7 before delegating to ba-pitch-analyzer (Map Scopes, step 8). Use it even when the user describes "read the code first and surface the unknowns" without naming Orient. Also accepts a tech-lead --order dispatch.
nguyenvanphituoc/shapeup-sdlc-plugin · ★ 2 · AI & Automation · score 68
Install: claude install-skill nguyenvanphituoc/shapeup-sdlc-plugin
# Orient — the Scout (Shape Up step 7) In Shape Up, the team that builds also **orients**: after kick-off they read the real code, spike the scary parts, and let reality generate **Discovered tasks** — which outnumber the imagined ones. This skill is that pass, made explicit. It exists because the orchestrator (`tech-lead`) must *delegate* orientation, and the generator (`task-executor`) can't host it: its first gate needs a task file, and **at Orient time no board exists yet** — the board is mapped *after* this pass, by `ba-pitch-analyzer` at step 8. So the Scout's whole job is to make the planner's board **reality-born instead of imagined**. It hands `ba` a map of where the pitch lands in real code, the findings from de-risking the single scariest area, and a seed list of tasks (imagined + already-discovered). Nothing more. ``` PO: shaping → bet → kick-off ──► tech-lead ──► ORIENT (you) ──► ba (Map Scopes) ──► build reads code, spikes, seeds ``` --- ## What the Scout is and is not | Does | Does NOT | |------|----------| | Read the kicked-off pitch + breadboard | Re-shape, re-bet, or question the appetite (PO already did) | | Trace pitch elements to real files/modules | Write production code | | Spike the **single** riskiest area, time-boxed | Build the scope board / tasks (that is `ba`, step 8) | | Seed the discovered-task list (imagined + discovered) | Keep `run-state` (tech-lead owns it) | | Emit raw hill **signal**