to-epic

This skill takes the current conversation context and codebase understanding and produces an epic. Do NOT interview the user — just synthesize what you already know.

Principles

Durability over precision

The epic may stay on backlog for days or weeks. The codebase will change in the meantime. Write the epic so it stays useful even as files are renamed, moved, or refactored.

• Do describe interfaces, types, and behavioral contracts
• Do name specific types, function signatures, or config shapes that the agent should look for or modify
• Don't reference file paths — they go stale
• Don't reference line numbers
• Don't assume the current implementation structure will remain the same

Behavioral, not procedural

Describe what the system should do, not how to implement it. The agent will explore the codebase fresh and make its own implementation decisions.