stride-ideation

Generate structured requirements documents from fuzzy ideas via round-based Q&A.

Updated May 12, 2026
One-click install
npx skills add https://github.com/cheezy/stride-ideation --skill stride-ideation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stride-ideation
Source: https://github.com/cheezy/stride-ideation/tree/main/skills/stride-ideation
Command: npx skills add https://github.com/cheezy/stride-ideation --skill stride-ideation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert vague feature or initiative ideas into a structured, reviewer-checked requirements document that’s ready to become Stride tasks.

Core Features & Use Cases

  • Round-based ideation loop: Collects Goal, Problem, Outcome, Assumptions, Constraints, Non-goals, and Success Metrics through batched questions with mandatory framing (round 3) and premortem (round 4).
  • Profile-guided prompts: Uses lean, product, discovery, or lean-startup profiles to tailor forcing questions and document augmentations.
  • Hard safety gates: Refuses to draft the document until all seven sections have substantive content, with additional shape requirements for Assumptions and Success Metrics.
  • Advisory requirements review: Runs an advisory requirements-reviewer pass to surface gaps and contradictions, followed by at most one refinement pass.

Quick Start

Use the stride-ideation skill to write a requirements spec for your idea by running the ideation command with an optional topic.

Frequently Asked Questions about stride-ideation

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

FAQPage Schema
How do I turn fuzzy product ideas into structured requirements?

To turn fuzzy product ideas into structured requirements, use a round-based Q&A loop to capture your Goal, Problem, Outcome, Assumptions, Constraints, Non-goals, and Success Metrics. This process enforces hard safety gates to ensure all sections have substantive content before generating a final markdown document.

What is a premortem checkpoint in requirements scoping?

A premortem checkpoint in requirements scoping is a mandatory review phase used to identify potential failures and rank riskiest assumptions. It occurs during the ideation loop, ensuring you surface and address critical project risks before finalizing your requirements document.

How do I define success metrics for a new feature spec?

To define success metrics for a feature spec, you must establish both leading and lagging indicators. The ideation process enforces shape requirements on these metrics, ensuring they accurately measure the desired outcome before the document passes its safety gates.

Does scoping ideation work with lean startup product profiles?

Scoping ideation works with lean startup product profiles by using profile-guided prompts. It tailors forcing questions and document augmentations specifically for lean, product, discovery, or lean-startup contexts to ensure the generated requirements fit your methodology.

How do I write ship-ready requirements from a vague feature idea?

To write ship-ready requirements from a vague feature idea, run an advisory requirements-reviewer pass after completing the Q&A loop. This surfaces gaps and contradictions, allowing at most one refinement pass before committing the final markdown document for Stride task decomposition.