메뉴
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/SethGammon/Citadel --skill workspace명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Focused research investigations. Converts questions into structured findings with confidence levels and source citations. Single agent by default; with --parallel (or when the question decomposes into 3+ independent angles) it spawns scout agents whose findings are compressed into a unified brief. Does not make decisions; produces information that informs the next step.
Unified router that auto-routes user intent to the right direct action, skill, orchestrator, or explicit Operation Control plan. Classifies input by scope, complexity, persistence needs, and parallelism, then dispatches to the cheapest path that can handle it: direct command, skill, marshal, archon, or fleet. Single entry point for all work.
First-run experience for the harness. Three modes: Recommended (guided, ~3 min), Full Tour (guided + skill walkthrough, ~8 min), and Express (zero questions, ~30 sec). Installs hooks first, detects stack, configures harness.json, runs a live demo on real code, and prints a reference card.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | workspace |
| license | MIT |
| description | Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context. |
| user-invocable | true |
| auto-trigger | false |
| trigger_keywords | ["workspace","multi-repo","cross-repo","across repos","multiple repos","coordinate repos","add redis and snowflake","split into repos"] |
| last-updated | "2026-03-29T00:00:00.000Z" |
| effort | high |
Do not use when:
/fleet or /archon).planning/workspace/session-{slug}.md — resume if status: active or needs-continueCLAUDE.md, check .planning/campaigns/ for active campaigns (avoid collisions)node .citadel/scripts/momentum-watch-start.cjs
node .citadel/scripts/momentum-read.cjs
Break the direction into repo-scoped work items (one campaign per repo per wave). Table format: # | Repo | Campaign Direction | Scope | Deps | Wave.
Rules: items with no deps → Wave 1; dependents → Wave 2+. Max 3 repo-campaigns per wave. Scope format: {repo}:{path}.
For each inter-wave dependency, specify the cross-repo contract: what the producer will produce, what the consumer expects, and where the contract lives (shared types package, OpenAPI spec, env var).
Create .planning/workspace/session-{slug}.md with frontmatter: version, id, status: active, started, completed_at: null, direction, repos (path + name + branch per repo), wave_count, current_wave: 1, campaigns_total, campaigns_complete: 0.
Body sections: Direction, Repos table (name/path/branch/status), Work Queue (table from Step 2), Cross-Repo Contracts (producer/consumer/contract/location), Wave Execution Log (per wave: status, campaigns, started, completed), Shared Context (discovery relay accumulation).
For each wave:
For each repo-campaign in this wave:
git checkout -b workspace/{slug}/{repo-name}/archon for complex (3+ phases), /fleet if parallelizable, /marshal or direct skill for simple (1-2 steps)momentum.json via node .citadel/scripts/momentum-read.cjs, inject as === PRIOR SESSION CONTEXT ===, skip if empty), cross-repo contracts, relevant CLAUDE.md sections from other reposExtract HANDOFF blocks, compress into cross-repo discovery brief, write persistent discovery records:
node .citadel/scripts/discovery-write.cjs \
--session {session-slug} --agent {repo-name}-{campaign-type} \
--wave {wave-number} --status {success|partial|failed} \
--scope "{repo-name}:{scope-path}" --handoff "{json-array}" \
--decisions "{json-array}" --files "{json-array}" --failures "{json-array}"
Write workspace/briefs/wave{N}-{repo-name}.md for each completed campaign.
Also write workspace/briefs/wave{N}-cross-repo.md summarizing:
For each cross-repo contract: verify the producer created the expected output (file + export for types, route existence for endpoints). If verification fails, flag and do not proceed with consumers.
Mark completed campaigns, update wave status, write discovery relay, advance current_wave.
status: completed, completed_at: {ISO timestamp}node .citadel/scripts/momentum-synthesize.cjs.planning/workspace/ does not exist: Create it (and workspace/briefs/).{monorepo}:{package-path} as the scope identifier.Disclosure: "Running multi-repo campaign across [repos]. Changes committed to each repo independently." Reversibility: red — coordinates changes across multiple repositories; cross-repo commits are hard to revert in bulk. Trust gates:
active state on completion---HANDOFF---
- Workspace: {slug} -- {direction summary}
- Repos: {N} repos, {M} campaigns across {W} waves
- Results: {completed}/{total} campaigns succeeded
- Branches: {list branches ready for review}
- Merge order: {suggested order based on dependency graph}
- Unresolved: {any failed campaigns or broken contracts}
---