ideation

Convert raw software ideas into templated Linear issues with architecture checks.

8|9|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/vibercoder79/KI-Masterclass-Koerting- --skill ideation-vibercoder79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideation
Source: https://github.com/vibercoder79/KI-Masterclass-Koerting-/tree/main/ideation
Command: npx skills add https://github.com/vibercoder79/KI-Masterclass-Koerting- --skill ideation-vibercoder79

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents teams from turning vague ideas into poorly scoped Linear issues by enforcing research, full architecture context loading, and sprint-fit scoring before anything gets created.

Core Features & Use Cases

  • Deep Research & Fact Verification: pulls in external facts via /research when needed and ensures acceptance criteria are grounded in verified details.
  • Architecture-Aware Story Drafting: loads the complete ARCHITECTURE_DESIGN.md (including all ADRs), checks SYSTEM_ARCHITECTURE.md and config/database impact, then generates a feature-grade Architecture Design Document (ADD) when appropriate.
  • Governance via Enforcement Checks: requires that every new architectural decision is either machine-enforced (guard location documented) or automatically triggers a suggested “Guard Story” for paper-only decisions.
  • Dependency Mapping & Sprint-Fit Scoring: drafts a story with bidirectional dependencies, estimates story points, evaluates carry-over risk, and only finalizes the Linear issue after operator approval.

Quick Start

Use the command /ideation when you have a new feature idea or need a well-written Linear issue with research, an ADD, and validated sprint fit.

Frequently Asked Questions about ideation

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

FAQPage Schema
How do I turn raw software ideas into ready Linear stories with architecture context?

To turn raw ideas into ready Linear stories, the ideation process loads complete architecture context, drafts an Architecture Design Document when needed, and generates a fully templated Linear issue with acceptance criteria and dependency mapping.

How does sprint planning work when sizing new features for Linear issues?

Sprint planning for new Linear issues works by scoring sprint-fit, estimating story points, evaluating carry-over risk, and mapping bidirectional dependencies before finalizing the issue for operator approval.

Do I need an Architecture Design Document for refactors and API integrations before creating Linear issues?

You need an Architecture Design Document for refactors and API integrations when architectural compatibility and dependency mapping must be decided upfront, ensuring new features are checked against system architecture and config impact.

What's the best way to enforce architectural guardrails when drafting Linear stories?

To enforce architectural guardrails when drafting Linear stories, every new architectural decision requires either a documented machine-enforced guard location or an automatically suggested Guard Story for paper-only decisions.

Can I add research and fact verification to Linear story acceptance criteria?

You can add research and fact verification to Linear story acceptance criteria by pulling in external facts during ideation, ensuring that all generated criteria are grounded in verified details before the story is finalized.

Why does my Linear story creation fail sprint-fit checks without dependency mapping?

Linear story creation fails sprint-fit checks without dependency mapping because the system requires bidirectional dependencies, story point estimates, and carry-over risk evaluation to be completed before operator approval and issue finalization.