Menü
Agent process spawning with provider configuration and execution
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | cfn-agent-spawning |
| description | Agent process spawning with provider configuration and execution |
| version | 1.0.0 |
| tags | ["agent-spawning","process-management","execution"] |
| status | production |
Parent Skill: cfn-agent-lifecycle Purpose: Spawn agent processes with proper environment and provider configuration
spawn-agent.sh - Primary agent spawning scriptspawn-worker.sh - Worker process spawningspawn-agent-wrapper.sh - Wrapper for standardized spawningspawn-templates.sh - Template-based spawningexecute-agent.sh - Agent execution handlerget-agent-provider-env.sh - Provider environment configurationparse-agent-provider.sh - Provider parsing utilitiescheck-dependencies.sh - Dependency validation# Spawn an agent
./.claude/skills/cfn-agent-lifecycle/lib/spawning/spawn-agent.sh \
--agent-type backend-dev \
--task-id "task-123" \
--provider kimi
# Execute agent directly
./.claude/skills/cfn-agent-lifecycle/lib/spawning/execute-agent.sh \
--agent-id "agent-123" \
--task "implement feature"
Tiered planning orchestrator. Runs the full SPARC+ pipeline (research, spec, decide, pseudo, data, arch, ux, design, test, ops) as a parallel DAG, scaled by build stage (mvp/beta/enterprise) via inclusion profiles. Enforces two gates: every success criterion is executable (verifiable-done) and every step is unambiguous (haiku-executable). Use as the entry point for any non-trivial build instead of cfn-spa-plan.
Post-planning completeness review. Extracts assumptions, traces dependencies, analyzes blast radius, checks alpha-readiness, surfaces gaps before implementation. Use after writing any plan that touches data, APIs, or shared state.
SPARC Specification phase. Make testable acceptance criteria, edge cases, pre/post conditions, invariants BEFORE planning implementation. Use when starting any non-trivial task to lock intent, surface ambiguity early.
Test-strategy phase of cfn-megaplan. Designs test depth properly: fixtures/test-data, the unit/integration/contract/e2e/load split, mocking strategy, and non-functional tests, instead of lumping everything into a vague red phase. Feeds Bar A (verifiable-done): every acceptance criterion becomes a concrete runnable check. Use after cfn-spec, cfn-arch, and (if frontend) cfn-ux.
Pre-edit backup + post-edit validation for safe file edits. Use to capture file state before edits, validate changes after edits, revert files to prior state, or ensure edit safety via auto backup/validation hooks.
Extract complete Redis coordination data from completed CFN Loop tasks and structure into comprehensive JSON analysis files