Skip to content

tibursocampos/agent-dev-toolkit / core/skills/orchestrate-analyze

orchestrate-analyze

Verified

Orchestrated Delivery O1: triage a feature, spawn conditional Agent specialists, write FEATURE.md + CONTINUITY + US/TS under features/NNN-slug/. No app code. Use when invoking /orchestrate-analyze.

references/triage.md

View on GitHub
**Intent entry (Step 1):** classify input and map to track before this table when O1 starts cold — load `intent-classification.md` first; early handoff to Classic SDD or Backlog Refine skips Step 0 Memory Bank Gate unless the operator continues O1 anyway.

---

## Triage decision table

| Dimension | Values | How to choose |
|-----------|--------|---------------|
| **Nature** | `greenfield` | New capability; little or no existing code to map |
| | `brownfield` | Touches existing modules, packages, APIs, or data |
| | `operational` | Ops/process/tooling (scripts, CI, sync) more than product domain |
| **Complexity** | `trivial` | One file / isolated fix; clear stack skill |
| | `medium` | Single story or small feature; Classic SDD often enough |
| | `complex` | Multi-story, unclear blast radius, or several `needs_*` true |
| **Scope** | `backend` / `frontend` / `fullstack` | Primary delivery surface |

| Complexity | Suggested path |
|------------|------------------------|
| `trivial` | `developer` / `*-developer` - skip full O1 unless user insists |
| `medium` | Classic SDD (`sdd-spec` -> …) **or** O1 if multi-US/TS |
| `complex` | Full Orchestrated Delivery O1 -> approval -> O2 |

If nature or any `needs_*` is unclear after a short Prior-context pass, ask the necessary high-cost questions, in blocks of at most 5. Default unset flags to `false`, **except** auth / secrets / PII / feed-token / supply-chain signals -> ask or set `needs_security=true`. Do not invent architecture in the parent orchestrator. Canonical spawn map: `ROSTER.md` only.

---

## Process — Collect description / promote

Ask for (or reuse Prior context): goal, current behavior, constraints, known repos/areas. Use selective memory-bank facts as Prior context - do not re-ask what the bank already states clearly.

If the user cites a `.md` **outside** `features/` (including a host plan file or any host plans dir): **Read** it and **promote** per `PIPELINE.md` § Promote — copy rich content (DDL, JSON, mermaid, tables, OpenAPI) into memory-bank phase 2 (`database-schema.md`, `api-contracts.md`, `component-catalog.md`, `config-examples.md` as relevant) and/or story `ARCH|SEC|ANALYSIS`. A citation is not Prior context until promote is done. Pointer-only / bibliography-only → **fail O1** (do not mark backlog approved). Allow Read of cited plans; never treat host plan files as O3 input.

Set complexity / nature / scope and `needs_*` per **Triage decision table** above and **canonical** `ROSTER.md` (do not fork a second mapping). Optional NuGet/examples: § Example: NuGet brownfield triage.

**Ambiguous flags:** ask at most a few high-cost questions in the user chat language. Do **not** invent architecture in the orchestrator. Prefer `false` until evidence or user confirms - **except** auth / secrets / PII / feed-token / supply-chain signals -> ask explicitly or set `needs_security=true`.

---

## Process — Trivial shortcut

If `trivial`: recommend skipping full O1 write. Render the prompt in the user chat language. Keep the option ids.

```text
Trivial scope. Prefer the shortcut?

1) /developer  (or the stack *-developer)
2) Continue O1 anyway (write the feature tree)
3) cancel
```

Only continue to allocate/scaffold if the user explicitly chooses **2**. Choosing **1** does not create story folders and does not present a partial backlog. If the feature still has an open question, the shortcut must not pretend the backlog exists. Either step 8c closes the FEATURE, or this shortcut stays a developer handoff with no `USnn` / `TSnn` / Bug folders.

## Example: NuGet brownfield triage (short)

**Ask:** Extract shared library X into an internal NuGet; App A and App B must consume it without breaking CI.

| Field | Value |
|-------|--------|
| Nature | `brownfield` |
| Complexity | `complex` |
| Scope | `backend` |
| needs_api | `true` (public package surface) |
| needs_domain | `true` (bounded context of shared types) |
| needs_database | `false` (unless shared persistence) |
| needs_frontend | `false` |
| needs_security | `true` (package feed / secrets / provide chain) |
| needs_devops | `true` (CI publish - CONTINUITY note only) |

**Spawn (parallel):** `repo-analyst`, `architect`, `security`.  
**Stories (example):**

| Id | Tipo | Título | Rationale | Product intent |
|----|------|--------|-----------|----------------|
| TS01 | TS | Package extract + internal feed publish | Upstream outcome; consumers depend on published package | n/a |
| TS02 | TS | App A consumes package without CI regression | Independent consumer / rollback boundary | n/a |
| TS03 | TS | App B consumes package without CI regression | Same pattern as TS02; separate blast radius | n/a |
| US01 | US | Developer publish flow documented | Optional user-facing outcome; not merged into TS01 | Who: package maintainer / Job: publish shared lib safely / Outcome: runbook-ready publish |

Full sizing anti-patterns and heuristics: `story-sizing.md` § Reference example: NuGet brownfield extract.

**After approve:** `/orchestrate-deliver - features/00N-nuget-extract/`
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall