Menu
Interactively create a new Evoloop story — auto-generates next ID, validates requirements and dependencies, writes both JSON and markdown files
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Show planning area readiness status -- statuses, open questions, blockers, and next actions
Clone an existing Evoloop story as a template for a new one — copies structure, resets status, prompts for changes to title, requirements, and dependencies
Estimate the total prompt size that will be sent to an AI agent when processing an Evoloop story — warns if approaching model context limits
Visualize the Evoloop story dependency graph as text tree and Mermaid flowchart — shows critical path, blocked chains, and ready-to-run stories
Run Evoloop doctor checks and auto-fix common issues — missing directories, non-executable scripts, missing templates, and provide remediation for manual fixes
Deep-dive into a specific story's state — stage, failures, dependencies, last agent output, requirement verification, and suggested next action
| name | new-story |
| description | Interactively create a new Evoloop story — auto-generates next ID, validates requirements and dependencies, writes both JSON and markdown files |
| disable-model-invocation | true |
| allowed-tools | ["Read","Glob","Grep","Bash(jq *)","Bash(mv *)","Write"] |
Glob prd/US-*.json, find max number, increment, zero-pad to 3 digits. Default: US-001.
Ask for each field interactively:
.plan/areas.md if exists, pick or customlow | medium | highsmall | medium | largeauto_deploy | gated_deploy.plan/work-breakdown.md, validate formatstrategy (string), healthChecks (array), rollbackTrigger (string), rollbackCommand (string), verification (array)Schema: id, title, area, priority, riskTier, sizing, autonomy, requirements[], dependencies[], stage: "build" (top-level), deploySafety{}, context{} (workBreakdown, traceability, runbook, areaDoc, files[]), status{} (planning, build, review, test, validation, deploy — all fresh/empty). Reference .plan/templates/story.template.json for exact shape.
Show complete JSON. Confirm before writing.
prd/<ID>.json via atomic write (jq → temp → mv)prd/<ID>.md from .plan/templates/story-tracker.template.md (substitute ID/title), or basic trackerCheck: required fields present, riskTier/sizing/autonomy enum values, requirements match REQ-###, deploySafety subfields complete.
Story created: <US-XXX> — <title>
Files: prd/<ID>.json, prd/<ID>.md
Area: <area> | Risk: <risk> | Size: <size>
Requirements: <N> | Dependencies: <N>
Next: ./orchestrator.sh run --tool claude --story <ID>