tibursocampos/agent-dev-toolkit / core/skills/orchestrate-analyze
orchestrate-analyze
VerifiedOrchestrated 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.5 KB |
| reference.md | markdown | 1.8 KB |
| references/arch-confirm.md | markdown | 4.0 KB |
| references/boundaries-handoff.md | markdown | 3.5 KB |
| references/command.md | markdown | 3.5 KB |
| references/intent-classification.md | markdown | 5.2 KB |
| references/memory-bank-gate.md | markdown | 881 B |
| references/must-not.md | markdown | 4.4 KB |
| references/process-common.md | markdown | 3.8 KB |
| references/spawn-map.md | markdown | 3.7 KB |
| references/story-synthesis.md | markdown | 18.8 KB |
| references/triage.md | markdown | 5.0 KB |
references/arch-confirm.md
View on GitHub## Architecture confirm gate (greenfield / `needs_domain`)
**When:** nature `greenfield` **or** `needs_domain=true` **and** no established in-repo / approved ARCH style.
**Flow (post-architect, before treating style as selected):**
```text
ARCH draft (4 sections) → operator confirm / adjust / cancel (localized labels, ids in `{{TOOLKIT_ROOT}}/skills/_shared/agents/QUESTIONS.md`) → ARCH approved
```
| Step | Rule |
|------|------|
| Draft | Architect proposes via `architecture-selection` + `prompts/architect.md`; optional scaffold `templates/features/story/ARCH/architecture-decision.md` |
| Confirm | Parent asks in the user chat language (`LANGUAGE.md`) (SKILL §7b). Silence, an ambiguous or unrelated reply, or a lone emoji is not approval; a clear affirmative reply in any language is. Receipt stays `needs-confirm.` until `confirm` |
| Approved | Persist final ARCH with style id; CONTINUITY notes decision; **point-promote** `memory-bank/architecture.md` (if not already) so it is not left draft / `needs-confirm`; Memory-bank status `refreshed`; implementers load **one** `principles/architecture/<style>.md` + matching stack overlay C |
| Brownfield | Skip **style re-pick / style-id confirm gate** only. Still spawn `architect` and `database` (when persistence is in scope) and write mirror ARCH (layers, DDL, EF vs Dapper or equivalent, pipeline). ARCH is **not** optional when `needs_domain` or brownfield. |
**Must not:** silent vertical-slice (or any) default; final ARCH before **sim**; glob all architecture overlays in O1.
Copy in the user chat language — see SKILL §7b.
---
## Process — Architecture confirm answers
When nature is **`greenfield`** **or** `needs_domain=true` **and** no established in-repo / approved ARCH style:
1. Architect returns an ARCH **draft** only (four sections per `prompts/architect.md`; may use `templates/features/story/ARCH/architecture-decision.md`).
2. Parent presents the draft and asks in the user chat language — copy in § Approval gate copy.
3. Act on the answer:
| Answer | Action |
|--------|--------|
| **sim** | Persist ARCH **approved**; record style id in CONTINUITY; **point-promote** / update `memory-bank/architecture.md` (if not already) so it is not left draft / `needs-confirm`; set Memory-bank status `refreshed`; continue synthesize |
| **ajustar** | Revise proposal with architect (or in-parent); re-present; ask again |
| **cancelar** | Leave draft; do **not** treat style as selected |
| *(silence / other)* | **not** approval — keep `needs-confirm.`; wait |
4. **Until sim:** do not write final ARCH; do not invent a silent default style (including vertical-slice). Brownfield with an established style: **skip this confirm gate** (style re-pick / style-id only) — still spawn `architect` and `database` (when persistence is in scope) and write a **mirror** ARCH slice (layers, DDL, EF vs Dapper or equivalent, pipeline). Do **not** skip ARCH because a style already exists.
See also § Architecture confirm gate.
---
## Approval gate copy (user chat language)
Render each gate in the user's conversation language, with the ids `confirm` / `adjust` / `cancel` as localized labels (see `{{TOOLKIT_ROOT}}/skills/_shared/agents/QUESTIONS.md`). The pt-BR blocks below are examples only, not templates.
### Backlog
```text
pt-BR example (render in the user's language):
Backlog O1 pronto em `{feature-path}`.
Posso marcar como aprovado e seguir para O2?
Options: confirm / adjust / cancel (localized labels)
```
RN01: silence, an ambiguous or unrelated reply, or a lone emoji is not approval; a clear affirmative reply in any language is.
### Architecture confirm (greenfield / `needs_domain`)
```text
pt-BR example (render in the user's language):
Rascunho ARCH (estilo proposto) em `{story-arch-path}`.
Posso gravar o ARCH aprovado com este estilo?
Options: confirm / adjust / cancel (localized labels)
```
Same rule: silence, an ambiguous or unrelated reply, or a lone emoji is **not** approval; keep `needs-confirm.` until `confirm`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |