Epic Outline

epic-outline

DEPRECATED in Speck v7. Use /speck-skeptical-review + /speck-decision-log instead — they replace the outline pattern with structured tradeoff enumeration and lockable decisions. The v6 epic-outline pattern (research mapping) is now embedded in /epic-plan's just-in-time research step. This skill r...

telum-ai/speck·0installs2stars

SKILL.md

Full skill instructions

The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).

User input:

$ARGUMENTS

⚠️ v7 Deprecation Notice

This skill is deprecated in Speck v7. The v6 epic-outline was a separate research-mapping step; in v7 that work is folded into:

/speck-skeptical-review — for enumerating alternatives at the epic's technical approach
/speck-decision-log — for locking the chosen approach with rationale and SHA stamp
/epic-plan — performs just-in-time research as needed (per the v7 just-in-time research pattern)

Recommended v7 path: /epic-clarify → /speck-skeptical-review (if approach unclear) → /epic-plan

This skill continues to work for v6 projects (back-compat). For new v7 work, prefer the path above.

⚠️ Step 0: Read Template First

Before any other action — read this template now using the Read tool:

.speck/templates/epic/outline-template.md

The template defines required sections and formatting for epic-outline.md. Reading it first tells you what research gaps and decision points to document.

Checkpoint: After reading, note the top-level sections from the template. Then continue to Step 1.

Create a technical outline that identifies key architectural decisions and research areas needed for epic implementation.

Load epic context:
- Find epic.md in current or parent directory
- Load project PRD.md for technical constraints
- Check for existing epic-outline.md
- Review other epics for integration patterns
- If no epic.md: ERROR "Run /epic-specify first"
Technical decision categories:

Architecture Decisions
- Component structure approach
- State management strategy
- API design patterns
- Data flow architecture
Technology Choices
- Libraries/frameworks needed
- Build vs buy decisions
- Integration approaches
- Testing strategies
Implementation Patterns
- Error handling approach
- Logging/monitoring strategy
- Security implementation
- Performance optimizations
Research need identification:
- Technology evaluation needs
- Best practice research
- Integration documentation
- Performance benchmarks needed
Generate epic outline:

CRITICAL: Load and follow the template exactly:
```
.speck/templates/epic/outline-template.md
```
Write output to: [EPIC_DIR]/epic-outline.md
Save as [EPIC_DIR]/epic-outline.md

Output summary:

✅ Epic Technical Outline Complete!

Key Decisions Identified: [X]
Research Areas: [Y] critical, [Z] important

Next Steps:
1. Use the just-in-time research pattern (`.cursor/skills/just-in-time-research/SKILL.md`)
   to address the outline’s highest-priority questions (web search first; generate a deep
   research prompt only if needed)
2. Then: /epic-plan

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/telum-ai/speck --skill epic-outline

View on GitHub

.cursor/skills/epic-outline/SKILL.md

project-specify
Load at the very start of a new project when the user describes what they want to build, or to update an existing project.md. Produces project.md — must run before project-clarify, project-context, and all downstream project commands. FIRST ACTION after loading: read template at .speck/templates/...
0 installs
epic-constitution
Load when an epic has unique technical principles that extend or override the project constitution. Produces epic-level constitution.md — optional, skip when the project constitution is sufficient for this epic's concerns.
0 installs
oauth-implementation
Load when implementing OAuth 2.0 and OpenID Connect authentication. Applies when building social login, SSO, PKCE flows, or integrating with OAuth providers like Google, GitHub, Apple.
0 installs
project-brainstorm
Load when a user has a vague idea, problem, or inspiration but isn't sure what to build. Use before /project-specify when the project concept needs crystallizing from loose thoughts into something concrete.
0 installs

More skills from telum-ai

telum-ai/speck

docker-containerization

Load when using Docker for containerizing applications. Applies when creating Dockerfiles, docker-compose setups, multi-stage builds, or optimizing container images.

2 0

View

telum-ai/speck

visual-quality

Enforce visual design quality in every UI file. Fires for .tsx, .jsx, .vue, .svelte, and similar component files. Ensures implementations express the project's design personality rather than producing generic/boilerplate UI.

2 0

View

telum-ai/speck

project-clarify

Load after project.md exists to fill gaps through targeted Q&A. Use when project goals, target users, or scope feel underspecified. Run before project-context or project-architecture to prevent rework downstream.

2 0

View

telum-ai/speck

story-outline

DEPRECATED in Speck v7. Use /speck-skeptical-review + /speck-decision-log instead — they replace outline-style research mapping with structured alternative enumeration and decision locking. /story-plan now performs just-in-time research inline. This skill remains for v6 compatibility but redirect...

2 0

View

telum-ai/speck

offline-first-architecture

Load when building offline-first applications that work without network connectivity. Applies when implementing local storage, sync queues, conflict resolution, or background sync.

2 0

View

telum-ai/speck

project-constitution

Load (Platform play level only) to define technical principles and architectural guardrails for the project. Produces constitution.md — optional but valuable when a team needs explicit coding standards, governance rules, or non-negotiable constraints. FIRST ACTION after loading: read template at ...

2 0

View

telum-ai/speck

posthog-integration

Load when integrating PostHog for product analytics and feature flags. Applies when implementing event tracking, A/B testing, session replay, or funnel analysis.

2 0

View

telum-ai/speck

project-validate

Load when all epics are validated and /audit has run for the project. Verifies the project meets its original vision and product-contract.md paid promise. Runs end-to-end JTBD smoke test via /larp across all personas. Declares a project-level readiness state. Produces project-validation-report.md...

2 0

View

telum-ai/speck

story-scan

Load for brownfield stories where existing code must be understood before planning. Use when a story extends, modifies, or integrates with significant existing functionality. Produces codebase-scan.md — skip for fully greenfield stories. FIRST ACTION after loading: read template at .speck/templat...

2 0

View

telum-ai/speck

serverless-architecture

Load when building serverless applications with AWS Lambda, Vercel Functions, or Cloudflare Workers. Applies when implementing FaaS patterns, managing cold starts, or optimizing serverless costs.

2 0

View

telum-ai/speck

epic-scan

Load for brownfield epics to analyze existing code patterns and implementations relevant to this epic's domain before planning. Use when the epic modifies or extends significant existing functionality. Skip for fully greenfield epics. FIRST ACTION after loading: read template at .speck/templates/...

2 0

View

telum-ai/speck

epic-analyze

Load after epic-tech-spec.md and epic-breakdown.md exist — quality check for consistency and completeness before any story work begins. Catches spec drift and missing coverage between the tech spec and story breakdown. FIRST ACTION after loading: read template at .speck/templates/epic/epic-analys...

2 0

View