메뉴
Stand up a new infiquetra agent-team repo end-to-end — context-library-compliant repo + Discord identity + GitHub identity + split-vault wiring + Ansible deploy harness — by composing a deterministic generator with two human-in-loop portal gates
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Route proposed Team Mimir profile behavior changes to target-owned Hermes dialogue.
Build a versioned Antigravity teammate delegation envelope and route it through the guarded agy wrapper.
Create durable Infiquetra implementation plans with issue, review, test, and deploy gates. Interrogates HOW work gets built, writes an agent-consumable plan artifact, records a plan saga, and routes to doc-review and /work. Triggers on "plan this", "how should we build this", "create a plan", "break this down", or a handoff issue ready for planning.
Coordinate a whole outcome as a durable DAG of leaf sagas. A level-triggered reconcile loop that dispatches the ready frontier to executors, harvests completion, and pages the operator only at gates and exceptions. The coordinator routes and never runs leaf work; status is derived on read. Thin coordinator verbs only — start, graph, advance, attend, resume, discover, handoff, attach — leaf work stays the native /resume, /work, /code-review, /qa.
Execute a settled Infiquetra plan to PR-ready, then own the round-N PR continuation loop. Restores and writes the work-thread saga (the primary writer), recommends an execution backend, runs risk-gated tests, calls /code-review programmatically and reads its envelope, gates hard on P0/P1 and stale reviews, and coordinates PR-open/review-request/merge under explicit confirmation — without owning deploy. Triggers on "build it", "work this plan", "execute the plan", "resume work on
Deep-dive one chosen Infiquetra idea into a right-sized requirements document before planning.
| name | team-scaffold |
| description | Stand up a new infiquetra agent-team repo end-to-end — context-library-compliant repo + Discord identity + GitHub identity + split-vault wiring + Ansible deploy harness — by composing a deterministic generator with two human-in-loop portal gates |
| when_to_use | Use this skill when the user: - Wants to create a brand-new agent team (a new persona or crew in the Olympus grouping or the Asgard grouping) - Says "scaffold a team", "stand up team-X", "add a new team", "new agent team repo" - Needs to reproduce the polyrepo per-team layout (deploy harness, vault slice, profiles/, engineering journal) without repeating the manual migration dance - Wants to promote an existing host-level agent into its own team repo - Asks how new teams get their Discord bot / GitHub App / vault tokens wired |
Automates "stand up a new team" end-to-end. The migration that created the first
12 teams (infiquetra/team-*) was a manual dance; this skill makes it
repeatable. It composes a deterministic Python pipeline (team-scaffold CLI,
in scripts/) with the two irreducible human gates that cannot be
API-automated.
Native
hermes profile installpackaging is DEFERRED. The deploy artifact is the Ansible harness (deploy/<team>.yml) that installs reusable role code frominfiquetra.hermes_teamand takes inventory/shared secrets as explicit inputs.
| Layer | Owner | Tool |
|---|---|---|
| repo skeleton, harness, vault wiring, inventory, identity stub | deterministic | team-scaffold CLI (scripts/) |
| Discord bot App create + token reveal (gate G1) | human | Chrome-MCP, per home-lab/Discord-Bot-Creation-Instructions.md |
| GitHub App create + install (gate G2) | human | home-lab/scripts/github_app_provision.py |
| SOUL authoring, per-profile runtime config | operator/creative | edit profiles/<n>/SOUL.md, deploy/team_profiles.yml |
Everything deterministic is idempotent and probes live state (repo exists? token vaulted? host in inventory?) — re-runnable and resumable across the gates.
cd scripts && uv venv && uv pip install -e ".[dev]"
uv run team-scaffold --help
Full detail in references/runbook.md; spec schema in references/input-contract.md. Summary:
team-spec.yaml (the one operator input) →
team-scaffold validate-spec team-spec.yamlgh repo create infiquetra/team-<name> --private (skip
if it exists).team-scaffold stamp team-spec.yaml --out <clone>
(context-library-compliant repo + deploy harness + authored stubs).profiles/<n>/SOUL.md (placeholder → real persona),
or pull the live SOUL for a promoted existing agent.deploy/team_profiles.yml (runtime config) →
team-scaffold validate-profiles deploy/team_profiles.yml.home-lab/Discord-Bot-Creation-Instructions.md. Then encrypt the revealed
token and splice it into the team vault:
ansible-vault encrypt_string --name vault_discord_bot_token_<persona> '<token>'
→ append to ansible/inventory/group_vars/all/vault.yml. (For a promoted
existing agent, instead: team-scaffold vault-wire team-spec.yaml --source <home-lab all.yml> --out <clone> to copy the block verbatim.)python3 home-lab/scripts/github_app_provision.py --app <persona> --org infiquetra.
Record the App slug + token-var NAME in identity/README.md (names only,
never the secret).set_bot_intents.py, discord_phase3.py) if the team needs channels.team-scaffold register-host team-spec.yaml (dry-run) →
... --apply, then commit home-lab's hosts.yml as a single revertible commit.INFIQUETRA_SHARED_INFRA_VAULT, then run ansible-playbook -i <inventory-artifact> --limit <host> deploy/<team>.yml --check --diff --vault-password-file ~/.vault_pass.txt.identity/ holds token-var NAMES only;
vault.yml holds only !vault-encrypted blocks (verbatim copies, same vault
password). The .gitignore excludes .env / vault-pass files.hosts.yml host
entry (step 9). Keep it last and as one commit so abort = git checkout hosts.yml.assert filter | length > 0 derived from profiles/) keeps each
team's deploy from touching its neighbor. Don't bypass it.host_group: orchestrator_vms) include the
hermes_orchestrator role and the orchestrator profile carries NO
discord_token_var (it posts as the conductor bot). The validators enforce this.cd scripts
uv run pytest -q # generator contract + validators + modules
uv run team-scaffold golden # re-derive the 12 known teams vs frozen fixtures
The harness tests prove the generator emits collection install, explicit
inventory/shared-vault inputs, and no legacy roles-path dependency. Run them
after any change to harness_gen.py or the specs.