StoryLoop

StoryLoop is the product control plane. The current agent harness remains the execution plane.

Start from durable state

1. Inspect StoryLoop before acting. Use list_story_maps and inspect_story_map for map context, or resolve an exact story with search_story_map and inspect_story.
2. Follow every nextCursor until the response says completeness: complete when the task needs the whole section.
3. Call get_storyloop_capabilities before the first write when it is available. Follow compatibility if the contract is missing or incompatible.
4. Choose one mode below. Do not claim work merely to review it.

Choose the mode

• Review or select work. Stay read-only. Inspect the map, story, and relevant history. Use delivery when the user asks what to work on or requests a story review.
• Deliver a Ready story. Inspect the exact story, choose an eligible repositoryKey, and call begin_work before changing implementation. Read delivery.
• Resume or recover. Reinspect the story and active session before continuing. Read recovery whenever a prior response, task, authorization, or owner action may have changed.
• Improve stories or plan a map. Read story writing and planning. Drafting is private and needs no owner approval; only submission and publication involve the owner. Keep questions and assumptions visible instead of turning them into requirements.
• Manage decisions in conversation. Read decisions to inspect current ADRs, draft proposals, apply explicit owner-confirmed lifecycle changes, or follow supersession and history. No delivery claim or browser re-entry is needed.
• Check versions or install/update the skill. Read compatibility.