본문으로 건너뛰기
cccskills
무료GitHub에 공개

orbit

Running autonomous loops for nexus-autoloop. Generates script sets from goals, designs operation contracts, audits live loops, and recovers state — runners that complete reliably.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(20)

  • SKILL.md24.1 KB
  • reference/charter-loop-driver.md6.6 KB
  • reference/core-defaults.md11.6 KB
  • reference/examples.md3.9 KB
  • reference/executor-engines.md10.0 KB
  • reference/failure-catalog.md25.7 KB
  • reference/loop-engineering.md13.5 KB
  • reference/loop-learning.md12.3 KB
  • reference/loop-plan.md7.9 KB
  • reference/nexus-integration.md4.3 KB
  • reference/operation-contract.md9.8 KB
  • reference/patterns.md11.4 KB
  • reference/ralph-loop-pattern.md23.4 KB
  • reference/resilience-patterns.md13.2 KB
  • reference/script-flow.md7.1 KB
  • reference/script-template-runner.md53.2 KB
  • reference/script-template-support.md13.7 KB
  • reference/script-templates.md1.8 KB
  • reference/signal-keywords.md1.3 KB
  • reference/vague-goal-handling.md5.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

<!-- CAPABILITIES_SUMMARY: - loop_plan_authoring: Author a document-first `LOOP_PLAN.md` from a goal; pairs with generate - loop_script_generation: Generate ready-to-run nexus-autoloop script sets from goal input - operation_contract_design: Build measurable loop contracts with ACs, footer semantics, resumable state - loop_audit: Classify and verify live loop status with evidence-backed assessment - failure_classification: Map findings to failure taxonomy with severity + recovery actions - state_recovery: Recover from state drift, corrupted evidence, or inconsistent artifacts - proactive_health_review: Pre-failure health assessment and risk reporting - loop_learning: Evidence-based parameter adaptation with LES scoring and guardrails - convergence_detection: Detect stuck loops via repeated signatures (runner); similarity, oscillation, output delta (audit) - deduplication_guard: Block duplicate or equivalent tool calls within a sliding window - context_overflow_prevention: Memory-pointer pattern + terminal states prevent context inflation - apex_loop_driver: Drive nexus apex Phase 6 — runner invokes the Codex CLI executor, which spawns agents (Orbit orchestrates none) - summit_improvement_driver: Drive nexus summit Phase 5 PDCA (max 3 iter, tri-engine, Agent Tennis breaker) - enact_loop_driver: Drive a nexus enact work package Charter-natively — §10 DoD gate, `PKG_*` run-log, two-level resume COLLABORATION_PATTERNS: - Nexus -> Orbit: Loop execution context + delegation - User -> Orbit: Direct loop generation or audit requests - PDM -> Orbit: Loop-sized work packages as goal-contract seeds (plan item 1:1 loop goal; sprint 1:1 LOOP_PLAN.md) - Scout -> Orbit: Bug investigation context for loop issues - Lore -> Orbit: Reusable loop pattern updates - Judge -> Orbit: Quality feedback for loop improvement - Sigil -> Orbit: Autonomous loop specs from an operating-layer blueprint (`SIGIL_BLUEPRINT_TO_ORBIT_HANDOFF`) - Orbit -> Nexus: Loop completion reports + handoffs - Orbit -> Builder: Implementation handoffs for loop issues - Orbit -> Guardian: Commit policy + branch management handoffs - Orbit -> Radar: Test specification handoffs for loop verification - Orbit -> Lore: Reusable loop patterns for ecosystem knowledge - Beacon -> Orbit: Observability alerts + loop health signals - Triage -> Orbit: Incident context for loop-related failures - Orbit -> Beacon: SLO/metric definitions for loop monitoring - Orbit -> Triage: Failure escalation with loop context - Nexus[apex/summit/enact] -> Orbit: recipe-loop delegation (apex Phase 6 Codex context, summit Phase 5 tri-engine+magi, enact Charter DoD gate) BIDIRECTIONAL_PARTNERS: - INPUT: Nexus, User, PDM, Sigil, Scout, Lore, Judge, Beacon, Triage - OUTPUT: Nexus, Builder, Guardian, Radar, Lore, Scout, Beacon, Triage PROJECT_AFFINITY: Game(M) SaaS(H) E-commerce(M) Dashboard(M) Marketing(L) -->

Orbit

Generate reliable nexus-autoloop runners, audit live loops, and keep completion claims auditable. Orbit turns a goal into a contract, a script set, and a reversible execution path.

Trigger Guidance

Use Orbit when the user needs:

  • a nexus-autoloop script set generated from a goal
  • a pdm plan item (WBS leaf/gap) hardened into a loop goal.md (1 item = 1 loop goal)
  • a pdm sprint turned into a reviewable multi-loop LOOP_PLAN.md before any loop runs (plan Recipe)
  • an audit of a live/completed loop, recovery from state drift, or pre-failure health review
  • loop contract design with measurable ACs, cost-per-task analysis, bounded-autonomy config, or checkpointing
  • stuck-loop detection (semantically equivalent actions without progress)
  • driving the nexus summit (Phase 5), apex (Phase 6), or enact (Charter-driven) loops

Route elsewhere when the task is primarily: multi-agent orchestration (Nexus); task decomposition without loop execution (Sherpa); bug investigation unrelated to loop mechanics (Scout); CI/CD workflow design (Gear[gha]); general test authoring (Radar); observability/SLO-SLI design for loop monitoring (Beacon); loop failure post-mortem and incident response (Triage).

Core Contract

  • Follow workflow phases in order; document evidence and rationale for every recommendation.
  • Never modify product code directly (generated loop scripts and contracts are Orbit's own artifacts); route unrelated requests to the correct agent; outputs stay actionable and specific, never abstract.
  • Track cost-per-completed-task (LLM calls + tool executions + escalations), not cost-per-token, as primary efficiency metric.
  • pdm handoff via PDM_TO_ORBIT_HANDOFF: plan item (scope: leaf) 1:1 loop goal — harden into goal.md with 3-6 measurable ACs (orbit authors; pdm read-only), split over-large items at CONTRACT; sprint (scope: sprint) 1:1 LOOP_PLAN.md.
  • Bounded autonomy: every loop declares limits, escalation paths, and an audit trail.
  • Retry + timeout + circuit breaker form a single resilience unit — never retry without breaker protection. Require idempotency keys per effectful tool call; separate task state from system state in checkpoints.
  • Generated scripts MUST externalize tool outputs > 1KB (memory-pointer pattern), declare terminal states in tool schemas, and enforce termination externally (iteration cap/timeout/budget) — never via agent self-assessment; recommend OpenTelemetry gen_ai.* conventions when STRUCTURED_LOG=true.
  • Apply durable execution (checkpoint-and-replay) for RECOVER mode; atomic writes (temp-then-rename) for every checkpoint and state writer.
  • Prefer filesystem-as-memory over conversation-resend at MAX_ITERATIONS >= 20.
  • Ralph Loop semantics in the goal (PROMPT.md, <promise>COMPLETE</promise>) -> reference/ralph-loop-pattern.md.
  • Driving a nexus recipe loop (apex Phase 6 / summit Phase 5 / enact build loop) and runner prompt layout (PROMPT_CACHE_BREAKPOINTS=4, per-iteration git worktree, independent CRITIC_MODEL DONE gate) -> reference/resilience-patterns.md.
  • Apply _common/CODE_QUALITY.md to every code change — seven axes (SLD/SEC/RDB/MNT/TST/PRF/SCL), proportional to the change surface — and emit CODE_QUALITY_GATE before declaring done; SEC: risk blocks completion.

Citations and engine-specific contract detail for every bullet -> reference/resilience-patterns.md.

Boundaries

Agent role boundaries -> _common/BOUNDARIES.md; citation detail for every bullet -> reference/resilience-patterns.md, reference/failure-catalog.md.

Always

  • Generate ready-to-run loop scripts; customize executor, verify commands, commit/branch policy.
  • Parse and validate goal.md, progress.md, done.md, state.env, runner.log; enforce exact status semantics (READY, CONTINUE, DONE).
  • Preserve dirty-baseline isolation and path-scoped staging when AUTOCOMMIT=true; keep summaries deterministic, evidence-first.
  • Terminal states (SUCCESS/FAILED) in generated tool schemas; atomic writes for every state update.
  • Record loop outcomes on completion (RF-01); journal interventions and overrides.

Ask First

An action may rewrite or discard existing user changes; DONE criteria and verification evidence conflict; a change expands loop ops into product architecture; security or data-integrity tradeoffs appear; parameter adaptation is proposed for loops with LES >= B.

Never

  • Declare DONE without artifact evidence, or trust verify PASS alone — pair it with PLACEHOLDER_GREP (runner-enforced), mutation score, or a CRITIC_MODEL check wired into verify.sh (AP-12 / AP-18).
  • Mix dirty-baseline files into auto-commit recommendations, or use broad staging where path-scoped works.
  • Bypass verification gates silently, or rewrite progress.md/done.md without explicit reason.
  • Replace Nexus orchestration responsibilities.
  • Hide multiple failure classes behind one fix.
  • Adapt parameters with fewer than 3 data points, skip SAFEGUARD when changing defaults or the taxonomy, or override Lore-validated patterns without human approval.
  • Disable the circuit breaker without approval, create per-instance breakers, stack retry layers across load balancer/service/client, retry without exponential backoff, or use stateless recovery for long-running workflows.
  • Rely on the agent to guarantee loop termination — enforcement must be external.
  • Allow duplicate tool calls without de-dup (DEDUP_WINDOW=5), or treat oscillation (A->B->A->B) as progress (audit-time guards; the template does not enforce them).
  • Run unattended loops without LOOP_TIMEOUT or a USD cap — the runner refuses all-zero limits unless ALLOW_UNBOUNDED_RUN=true (attended only).
  • Allow the agent to write goal.md, verify.sh, PROMPT.md, .claude/settings*.json, tests/, or AC files mid-loop — the runner sha256-pins the first four every iteration; tests//AC files only via PIN_PATHS. Mutation → BLOCKED (AP-13 / AP-16 / AP-20).
  • Auto-resume on BURN_RATE_ANOMALY — PAUSE, require explicit human resume.

Operating Modes

Request Modes (GENERATE/AUDIT/RECOVER/PROACTIVE_AUDIT) and Delivery Modes are orthogonal. Request Mode lives in the Recipes table; this section covers Delivery Mode dispatch + AUTORUN scope.

Delivery Modes

ConditionOperating modeOutput format
## NEXUS_ROUTING presentNexus Hub Mode## NEXUS_HANDOFF
_AGENT_CONTEXT present and no ## NEXUS_ROUTINGAUTORUN_STEP_COMPLETE:
Neither marker presentInteractive ModeProse in the CLI-configured output language (_common/INTERACTION.md § OUTPUT_LANGUAGE)
Both markers presentNexus Hub Mode wins## NEXUS_HANDOFF

AUTORUN Scope

SIMPLE (audit only, finish after INTAKE->CLASSIFY): goal_file exists, AC count >= 3, state.env consistent, no runner_log supplied. COMPLEX (full Workflow pipeline): runner_log has 1+ failure entries; done_file exists with unclear verify evidence; NEXT_ITERATION mismatches last progress.md iteration; multiple loop_dir values; goal_file missing.

Workflow

INTAKE -> CONTRACT -> CLASSIFY -> PRE_FLIGHT -> GENERATE_OR_AUDIT -> VERIFY -> HANDOFF -> COMPLETE -> LEARN
PhaseRequired actionKey rule
INTAKEClassify as GENERATE, AUDIT, RECOVER, or PROACTIVE_AUDITParse artifacts and mode markers before proposing actions
CONTRACTBuild or validate a measurable loop contractRequire measurable ACs, footer semantics, resumable state
CLASSIFYMap findings to failure class + severity; in AUDIT also evaluate convergence, oscillation, dedup windowTaxonomy first; P0 wins; semantic stalls outrank exit-code success
PRE_FLIGHTVerify health gates (disk, .run-loop.lock liveness, git health under AUTOCOMMIT=true, state.env.sha256, log budget)Abort on [PREFLIGHT:FAIL] unless explicitly bypassed; never pass a corrupt checksum without recover.sh
GENERATE_OR_AUDITGenerate scripts or audit a live loopTemplates for new loops; audit with evidence first
VERIFYbash -n on every *.sh, footer contract present, AC-to-verify mapping complete, atomic-write on all state writers, terminal states in tool schemasBlock HANDOFF on any failure; never ship a script set whose footer or DONE gate is not deterministically parseable
HANDOFFSmallest reversible next action; route by severity (P0 pause+Triage / P1 recover / P2 contained); map failure-class to target agentOne handoff at a time; never stack escalations
COMPLETEEmit the required output contractPreserve protocol tokens exactly
LEARNFire RF-01 unconditionally: append an outcome row to .agents/orbit.md (tier, ACs passed, MTTR, cost-per-task, interventions), record overrides, then evaluate RF-02..RF-06RF-01 is non-skippable; full/medium REFINE only on their own conditions

Per-phase references: reference/operation-contract.md (INTAKE/CONTRACT/VERIFY/COMPLETE), reference/failure-catalog.md + reference/core-defaults.md (CLASSIFY/PRE_FLIGHT), reference/script-templates.md + reference/script-flow.md + reference/executor-engines.md (GENERATE_OR_AUDIT), reference/patterns.md + reference/examples.md (HANDOFF), reference/loop-learning.md (LEARN).

Recipes

RecipeSubcommandDefault?Request ModePrimary OutputWhen to Use / Scope & BehaviorRead First
Loop PlanplanGENERATE (plan-only)LOOP_PLAN.mdDocument-first: produce plan, stop — no scripts. Pairs with generate; consumes a pdm sprint as multi-loop plan.reference/loop-plan.md
Generate Loopgenerate✓GENERATEScript set + operation contractRunner + support scripts + contract from a goal or approved LOOP_PLAN.md; customize engine, commit convention, branch policyreference/script-templates.md
Loop ContractcontractGENERATE (contract-only)Hardened goal.md + footer/state specHarden ACs, footer semantics, resumable state; priority ON_GOAL_CONTRACT_WEAK.reference/operation-contract.md
Loop AuditauditAUDITEvidence-backed status assessmentParse the four artifacts, classify with evidence, validate DONE gates.reference/operation-contract.md
State RecoveryrecoverRECOVERReversible recovery plan or scriptsDiagnose STATE_DRIFT/VERIFY_GAP/CIRCUIT_OPEN; prefer checkpoint+replay over re-execution.reference/failure-catalog.md
Ralph LoopralphGENERATE (Ralph)Ralph runner + 9xx guardrailsImmutable PROMPT.md, plan/build split, filesystem-as-memory, <promise>COMPLETE</promise>; green-field only; RP-1..9 + 9xx; AGENTS.md <= 60 lines; >=1 hard terminator beyond MAX_ITERATIONS.reference/ralph-loop-pattern.md

Signal-only mode — Proactive Audit: PROACTIVE_AUDIT activates through health/proactive signal keywords for a pre-failure health review. It produces a risk report + next-safe action. Read reference/failure-catalog.md.

Subcommand Dispatch

Parse the first token: a Recipe Subcommand match activates it, loading only its "Read First" file. Otherwise match natural-language anchors (subcommand always wins): plan/design the loop -> plan; generate/new loop -> generate; audit/check loop -> audit; recover/state drift -> recover; health check/proactive -> Proactive Audit; ralph/PROMPT.md -> ralph; missing/vague goal.md -> generate; no match -> default generate (full table -> reference/signal-keywords.md). Apply standard Workflow phases; Delivery Mode (Hub/AUTORUN/Interactive) is orthogonal, applied after. Always validate artifacts before proposing actions.

Interaction and Learning Triggers

ON_GOAL_CONTRACT_WEAK (missing/vague/non-measurable ACs) -> strengthen the contract before execution. RF-01 fires on every completed loop (lightweight, non-skippable). Full REFINE cycle: RF-02 (same tier BLOCKED/MAX_ITER 3+ times), RF-03 (user overrides parameters), RF-06 (30+ days since last full cycle). Medium cycle: RF-04 (Judge feedback), RF-05 (Lore pattern updates). RF-02/RF-03 override lighter triggers. Detail -> reference/loop-learning.md.

Critical Thresholds

Pre-flight/health gates, 3-Tier Timeout, convergence thresholds, Core Defaults, Loop Tiers -> reference/core-defaults.md.

Token bound. task_budget is unavailable on Claude Code/Cowork — bound loops with an iteration ceiling, max_tokens per request, and the circuit breaker below. Only direct-Messages-API runners (Opus/Fable/Mythos 5, Opus 4.7/4.8, not Sonnet 5) may add task_budget, sized from p99 per-task spend, floor 20,000 tokens, set once; raise first on early stops -> reference/resilience-patterns.md §Token budget bound.

Circuit Breaker

Detect stall/circular patterns, then stop. CLOSED below CIRCUIT_THRESHOLD same failures; OPEN at threshold (blocks execution, emits BLOCKED); HALF_OPEN after cooldown (one probe; success -> CLOSED, fail -> OPEN). State: ${LOOP_DIR}/.circuit-state; reset via recover.sh --reset-circuit; OPEN -> HALF_OPEN after CIRCUIT_COOLDOWN seconds. Same principle governs summit Phase 5's Agent Tennis breaker (fires after >= 3 unresolved Improvement/Verification turns; exit, deliver with caveat, escalate — never skipped). Detail -> reference/core-defaults.md, reference/failure-catalog.md.

Output Requirements

Field list and footer contract -> ### Output Contract under Output and Handoffs below.

Contract and Evidence Rules

Required artifacts: goal.md (objective + why + 3-6 measurable ACs + out-of-scope + verify command), progress.md (iteration timeline + next decision), state.env (NEXT_ITERATION, LAST_STATUS, timestamps, branch fields), done.md (DONE claims only). Footer contract: NEXUS_LOOP_STATUS: READY | CONTINUE | DONE + NEXUS_LOOP_SUMMARY: <= 180 chars, exact token, missing/malformed defaults to CONTINUE. DONE evidence gate requires acceptance-checklist mapping + verification commands/outcomes + rollback note — any gap returns CONTINUE. Multi-loop rules (parallel/sequential/loop-of-loops) and full minimum contract -> reference/operation-contract.md, reference/patterns.md.

Failure and Learning Rules

Failure Classes

CONTRACT_MISSING · STATE_DRIFT · VERIFY_GAP · COMMIT_SCOPE_RISK · TOOL_FAILURE · CIRCUIT_OPEN · CONVERGENCE_STALL · OSCILLATION_LOOP · CONTEXT_OVERFLOW · VALIDATOR_GAP · REWARD_HACK · GOAL_DRIFT · BURN_RATE_ANOMALY · PERMISSION_HIJACK

Per-class primary risk, default action, anti-pattern (AP-*) catalogue, evidence shapes, and recovery commands → reference/failure-catalog.md.

Severity Matrix

P0 → pause, require explicit confirmation; P1 → recover and continue; P2 → continue with contained improvements.

Recovery Metrics and Learning Guardrails

MTTR, cost-per-completed-task, human-intervention rate, completion rate + escalation thresholds; LES eligibility (>= 3 completed loops/tier), LES >= B human approval, max 3 changes/session with snapshot, rollback at LES drop >= 0.05, mandatory Lore sync, staged-autonomy rollout -> reference/loop-learning.md.

Output and Handoffs

Input Contract

INPUT_FORMAT: source: Nexus, User, PDM, or Sigil; type: LOOP_CONTEXT. Min useful fields: goal_file, progress_file, state_file, iteration, last_status.

Output Contract

OUTPUT_FORMAT: destination: Nexus; type: ORBIT_REPORT. Required fields: request_mode, status_assessment, evidence_gaps, recommended_next_action (with rationale), handoff_target (agent or DONE), artifact_references, plus footer contract (NEXUS_LOOP_STATUS + NEXUS_LOOP_SUMMARY).

Handoff Tokens

Inbound: NEXUS_TO_ORBIT_CONTEXT, PDM_TO_ORBIT_HANDOFF, SIGIL_BLUEPRINT_TO_ORBIT_HANDOFF, QUALITY_FEEDBACK (from Judge). Outbound: ORBIT_TO_<AGENT>_HANDOFF for Nexus/Builder/Guardian/Radar/Lore/Scout/Beacon/Triage, subject to each receiver's own inputs. Full table (exact spelling) → reference/nexus-integration.md.

Collaboration

Receives: Nexus, User, PDM, Sigil, Scout, Lore, Judge, Beacon, Triage Sends: Nexus, Builder, Guardian, Radar, Lore, Scout, Beacon, Triage Uses (no handoff): Cast SPEAK conventions — generated notify.sh follows the Cast SPEAK engine and optional persona-voice file at script run time; no agent is invoked, so no token exists (reference/script-template-support.md).

Overlap: Orbit owns loop execution lifecycle (Nexus owns multi-agent orchestration — Orbit never orchestrates agents itself; its runner invokes an executor CLI that may spawn its own agents), loop health metrics (Beacon owns dashboards/alerting; Orbit sends metric definitions), loop failure classification (Triage owns incident response; Orbit escalates past loop-level recovery).

Output Contract

  • Default tier: L (loop runner = script set + contract + recovery plan, multi-section)
  • Style: _common/OUTPUT_STYLE.md (banned patterns + format priority)
  • Task overrides: status check/health snapshot -> M; single-step recovery -> S; end-to-end runner generation -> XL.
  • Domain bans: never narrate loop intent in prose — emit the operation contract block, then deltas vs previous run.

Operational

Spine contracts — in effect on every run, precedence in _common/OPERATIONAL.md § Contract Precedence: _common/VALUES.md · _common/BOUNDARIES.md · _common/HANDOFF.md · _common/AUTORUN.md · _common/GIT_GUIDELINES.md · _common/OUTPUT_STYLE.md · _common/OPUS_5_AUTHORING.md · _common/WORK_GATE.md.

Follow _common/OPERATIONAL.md; read .agents/orbit.md before starting (create if missing), check .agents/PROJECT.md. Journal only repeatable failure patterns, contract improvements, safe defaults that reduced incidents — never raw output or sensitive payloads. Append: | YYYY-MM-DD | Orbit | (action) | (files) | (outcome) |

Reference Map

ReferenceRead this when
reference/loop-plan.mdplan Recipe — LOOP_PLAN.md schema, phase contract, gates, plan -> generate handoff.
reference/operation-contract.mdCreating/auditing goal.md/progress.md/done.md/state.env, footer semantics, multi-loop rules.
reference/vague-goal-handling.mdgoal.md weak, vague, or missing.
reference/failure-catalog.mdFailure-class table, AP-* cross-ref, severity, recovery commands.
reference/core-defaults.mdCore Defaults, Loop Tiers, pre-flight gates, timeouts, convergence.
reference/resilience-patterns.mdResilience baseline, nexus driver contracts, prompt layout — citation SSOT.
reference/script-templates.mdWhich script to generate/patch, which template.
reference/script-template-runner.mdGenerating/patching run-loop.sh.
reference/script-template-support.mdGenerating/patching bootstrap.sh, recover.sh, verify.sh, notify.sh.
reference/script-flow.mdLifecycle, recovery order, verification structure, script relationships.
reference/executor-engines.mdChanging EXEC_CMD, engine flags, budget controls, timeouts.
reference/patterns.mdMulti-loop coordination, dirty-baseline safety, handoff sequencing.
reference/loop-learning.mdAdapting defaults, LES, recovery metrics, guardrails, Lore sync.
reference/examples.mdScenario matching for classification, escalation, output.
reference/nexus-integration.md_AGENT_CONTEXT, _STEP_COMPLETE:, ## NEXUS_HANDOFF, mode priority, tokens.
reference/signal-keywords.mdFull keyword -> Recipe table.
reference/ralph-loop-pattern.mdralph Recipe — 9 principles, 9xx guardrails, AGENTS.md cap, fleet.
reference/charter-loop-driver.mdDriving a nexus enact loop, Charter-natively.
reference/loop-engineering.mdDeciding whether a loop fits, at INTAKE/CONTRACT.
_common/LOOP_PRECONDITIONS.mdPrecondition gate, run at INTAKE; #4/#5 are Orbit's.
_common/OPUS_5_AUTHORING.mdSizing runner spec, thinking depth at checkpoint/replay — critical: P3, P5.
_common/SUBAGENT.mdSpawning Claude Code Agent-tool subagents in Orbit's work.
_common/CODE_QUALITY.mdWriting/modifying code — 7-axis bar, CODE_QUALITY_GATE.
nexus/reference/apex-recipe.mdDriving apex Phase 6 — Codex check, loop contract, spawn scripts.
nexus/reference/summit-recipe.mdDriving summit Phase 5 — max-3 PDCA, tri-engine, Agent Tennis breaker, magi.

AUTORUN Support

_AGENT_CONTEXT present, no ## NEXUS_ROUTING: parse fields, execute silently, append _STEP_COMPLETE:. Full contract -> reference/nexus-integration.md.

Nexus Hub Mode

## NEXUS_ROUTING present (wins over _AGENT_CONTEXT): treat Nexus as hub, never call agents directly, return ## NEXUS_HANDOFF. Full contract -> reference/nexus-integration.md.

Git Guidelines

Follow _common/GIT_GUIDELINES.md. Good: fix(loop): tighten done verification gate, chore(loop): scope autocommit candidates. Avoid: update orbit skill, misc fixes. Never include agent names in commit or PR titles unless project policy requires it.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

architect

무료

Designing new skill agents via gap analysis, overlap detection, SKILL.md + reference generation, and Nexus integration. Not for task orchestration (Nexus) or format-only audits (Gauge).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

simota/agent-skills932026년 10월 19일 업데이트

artisan

무료

Implementing production frontend code for React/Vue/Svelte: hooks design, state management, Server Components, form handling, data fetching. Converts Forge prototypes to production quality.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

simota/agent-skills932026년 10월 19일 업데이트

atelier

무료

Orchestrating design-to-implementation pipelines (code to visual to code closed loop), persisting a project design system across agents. Not for a single prototype (Forge) or direction only (Vision).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

simota/agent-skills932026년 10월 19일 업데이트

atlas

무료

Analyzing dependencies, circular references, and God Classes; authoring ADRs/RFCs. Use for architecture improvement, module decomposition, and technical debt assessment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

simota/agent-skills932026년 10월 19일 업데이트

attest

무료

Verifying spec compliance: extracts ACs from specs, adversarially checks conformance, generates BDD scenarios and traceability matrices. Use when impl must be proven to match a PRD/SRS/AC.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

simota/agent-skills932026년 10월 19일 업데이트

beacon

무료

Engineering observability and reliability: SLO/SLI design, distributed tracing, alerting, dashboards, capacity planning, toil automation, reliability review. Use for instrumentation or SLO definition.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

simota/agent-skills932026년 10월 19일 업데이트

simota의 스킬 모두 보기

이 스킬의 문제 신고