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/process-common.md

View on GitHub
## Process — Caveman (Lite cap)

1. Read `{{SDD_ROOT}}/preferences.json` (create `{ "caveman_mode": false, "caveman_level": "full" }` if missing).
2. If `caveman_mode` is false: continue without compression.
3. If true: load `{{TOOLKIT_ROOT}}/skills/_shared/caveman/CAVEMAN.md`; apply **Lite** participation cap + prefs `caveman_level` (Lite skills never escalate); show once: `[Caveman] Modo ativo (respostas compactas, level={effective}). Digite caveman off para desativar.`
4. Honor `caveman on|off|status|lite|full|ultra` (and `stop caveman` / `normal mode`) during the session.
5. Auto-Clarity + never-compress gates/drafts/paths per `CAVEMAN.md`.

---

## Process — Resolve storage

Load `STORAGE.md` + `STORAGE-RESOLUTION.md`. Run resolution with `$Workflow = classic`. Resolve feature root and bank root:

- **repository** -> feature `$Cwd/features/`; bank `$Cwd/memory-bank/`
- **global** -> feature `<classic.path>/features/`; bank `<classic.path>/memory-bank/`

**Path sanitize (required)** for any invoke / allocated feature path: normalize (`\` -> `/`, trim trailing `/`, resolve `.`). Reject if it contains `..`, or if the resolved absolute path is **not** under the feature root above. Ask again, in the user's language, for a canonical path - do not Read/Write outside the feature root.

If first run for this repo: ask storage in the user chat language per `STORAGE.md` and persist manifest. Confirm target workspace. Do **not** invent a feature path outside the resolved root.

Repository mode: ensure SDD `.gitignore` patterns per `STORAGE.md` and `features_versioned` in manifest when writing under `features/` or `memory-bank/` (**do not** add `/memory-bank/`; keep `docs/documentation-plan/plan.md` ignored without a negation rule; do not weaken toolkit patterns; never ignore `skills/`). **Global mode:** do not edit project `.gitignore`.

---

## Process — Backlog approval + O2 handoff

Before asking: **product artifact quality gates** must pass (`references/story-synthesis.md` § Product artifact quality gates — FEATURE depth TE01, promotion TE02, cap ≤4 / RN03). Required specialist folders must exist on disk for true flags / brownfield (`ANALYSIS/` / `ARCH/` / `SEC/` per `ROSTER.md`); cited non-feature `.md` must be promoted (not pointer-only). Else **fail O1** — do not present the backlog as ready and do **not** mark approved.

Present the backlog (feature summary + story table with **Rationale** column + scorecard highlights). Ask in the user chat language — copy in `references/arch-confirm.md` § Approval gate copy — with ids per `core/skills/_shared/agents/QUESTIONS.md`.

| Id | Action |
|----|--------|
| `confirm` | status -> `approved`; continue O2 handoff |
| `adjust` | revise stories/flags; re-present; ask again |
| `cancel` | leave `draft`; do not hand off to O2 |
| *(silence / ambiguous / unrelated reply)* | **not** approval - wait |

On `confirm`:

1. Update `FEATURE.md` / story statuses to `approved` as appropriate.
2. Update `CONTINUITY.md`: phase stays `analyze` until O2 starts (or set handoff-ready note); `Last agent` = `orchestrate-analyze`; keep Memory-bank fields; typed handoff string.
3. Offer O2 (document series vs parallel as **O2 choice** - do not implement O2 here) — `references/boundaries-handoff.md` § Canonical handoff strings.

Remind in the user chat language: O2 will ask série vs paralelo for per-story PRD/PLAN.

---

## Process — Durable progress handoff

Checkpoint durable workflow progress at the workflow-defined boundaries; context usage does not add a stop gate.

1. Persist latest `CONTINUITY.md` (estado atual short per CONTINUITY template, decisões, pendências, exact next `/…`).
2. Offer session handoff - same phase, resume with feature path:

```text
/orchestrate-analyze - <portable-feature-path>
```

Do **not** paste full specialist dumps into the parent chat.
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: 469kUpdated 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: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated 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: 321kUpdated Claude CodeCodexVerifiedInstall