story-outline

Analyze story specifications to generate technical outlines with research questions.

2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/telum-ai/speck --skill story-outline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-outline
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/story-outline
Command: npx skills add https://github.com/telum-ai/speck --skill story-outline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill analyzes a story specification to identify technical decisions that require research, preparing the groundwork for the planning phase and reducing ambiguity.

Core Features & Use Cases

  • Technical Context Identification: Extracts and categorizes technical requirements like languages, dependencies, storage, and testing needs from a story's spec.md.
  • Research Area Detection: Pinpoints unfamiliar technologies, architectural decisions, and performance requirements that necessitate further investigation.
  • Use Case: When a new story is defined, this Skill can automatically generate a technical outline, flagging areas where the team needs to research best practices or compare different technology options before implementation begins.

Quick Start

Analyze the current story specification and generate a technical outline with research areas.

Frequently Asked Questions about story-outline

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

FAQPage Schema
How do I analyze a story specification to identify technical decisions and dependencies?

To analyze a story specification, you can process the `spec.md` file to automatically extract technical context like languages, dependencies, storage, and testing needs, resulting in a detailed technical outline for planning.

What is the best way to detect research areas in a development workflow before implementation?

Detecting research areas in a development workflow involves pinpointing unfamiliar technologies and architectural decisions within a story specification, generating prioritized research questions to reduce ambiguity before implementation begins.

How do I extract technical context like performance goals and target platform from a spec file?

Extracting technical context from a spec file requires analyzing the story specification to identify and categorize requirements including language, primary dependencies, target platform, performance goals, constraints, and scale.

Can I automatically generate a technical outline for my project planning phase?

Yes, you can automatically generate a technical outline by analyzing your story specification to outline required technical decisions and dependencies, outputting a structured `outline.md` file detailing technical context and research areas.

When do I need to generate a technical outline for a story specification?

You need to generate a technical outline when a new story is defined and you must prepare the groundwork for the planning phase, flagging areas where the team needs to research best practices or compare technology options.