skills.rest
steilerDev
steilerDevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

epic-start

Orchestrate six-step epic planning workflows with role-based tasks and artifacts.

4|3|Updated Feb 7, 2026
Search Tags:#planning#architecture#github#backlog#issues#epic#product-management
One-click install
npx skills add https://github.com/steilerDev/cornerstone --skill epic-start
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-start
Source: https://github.com/steilerDev/cornerstone/tree/main/.claude/skills/epic-start
Command: npx skills add https://github.com/steilerDev/cornerstone --skill epic-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The planning process for new epics is often fragmented across teams. This skill orchestrates a structured, step-by-step workflow to transform high-level epic ideas into actionable plans with defined owners, architecture decisions, and acceptance criteria.

Core Features & Use Cases

  • Structured six-step planning process: Rebase, wiki sync, product owner planning, product architect design, plan presentation, and handoff with clear ownership and artifacts.
  • Role-resolved workflow: Delegates tasks to product-owner and product-architect agents, coordinating dependencies and sprint assignments.
  • Use Case: At the start of a new epic, generate a complete planning plan with tasks, milestones, and documentation references for leadership review.

Quick Start

Initiate the epic planning workflow and follow the six steps in order.

Frequently Asked Questions about epic-start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan epics with clear ownership and architecture design?▼

Epic planning with clear ownership is structured through a six-step workflow that decomposes requirements into stories, defines architecture decisions, and prepares stakeholder approvals across product, architecture, and project management roles.

What is the best way to decompose epic requirements into actionable stories?▼

Decomposing epic requirements into actionable stories is handled by role-resolved planning, delegating tasks to product-owner and product-architect agents to coordinate dependencies and sprint assignments.

How do I sync GitHub issues and wiki documentation during epic planning?▼

Syncing GitHub issues and wiki documentation during epic planning is executed through the initial git rebase and wiki synchronization steps before generating role-based planning artifacts.

Can I use this workflow to generate architecture decision records for stakeholder approval?▼

Generating architecture decision records for stakeholder approval is supported via the product architect design phase, which updates ADRs and prepares concrete prompts for leadership review.

Does epic planning require a specific project management framework to work?▼

Epic planning does not require a specific project management framework, as the workflow orchestrates generic product, architecture, and project management roles to assign sprints and handoff procedures.

When should I not use a structured six-step epic planning process?▼

Structured six-step epic planning should be avoided for isolated, low-complexity issues that do not require cross-team coordination, architecture decisions, or stakeholder approvals.

Related Skills

Explore More Product & Management Skills→
dyoshikawadyoshikawa
1

rebase-latest-main

Rebase a local git branch onto the latest remote main.

Community
Intermediate
sunholo-datasunholo-data
33

AILANG Sprint Executor

Execute approved sprint plans with test-driven development and lint checks.

Official
Intermediate
anhhung04anhhung04
1

github-triage

Automate task creation and status updates from GitHub issues via the API.

Community
Basic
andersnygaardandersnygaard
5

task-board

Transform user requests into structured implementation plans with dependencies and risks.

Community
Basic