blade-storm

Turn vague feature ideas into structured technical design documents.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/tiantien/team-ai-coding-plugin --skill blade-storm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blade-storm
Source: https://github.com/tiantien/team-ai-coding-plugin/tree/main/skills/blade-storm
Command: npx skills add https://github.com/tiantien/team-ai-coding-plugin --skill blade-storm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn vague product ideas into clear, validated technical direction before writing code. It reduces back-and-forth by guiding users from an unclear request to a concrete, implementation-ready design.

Core Features & Use Cases

  • Progressive clarification: Asks one focused question at a time to uncover goals, users, constraints, and success criteria.
  • Solution exploration: Compares 2-3 distinct approaches so the user can choose a sensible path instead of guessing.
  • Stepwise design review: Breaks the design into small sections and confirms each part before continuing.
  • Handoff-ready output: Produces a structured design document that can flow into downstream specification and development work.
  • Use case: A product owner says they want "a notification center" but has not defined the audience, delivery rules, or failure handling; this Skill helps shape the idea into a dependable design brief.

Quick Start

Use the blade-storm skill when you want to turn a rough feature idea into a clear technical design through guided discussion.

Frequently Asked Questions about blade-storm

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

FAQPage Schema
How do I turn a vague product idea into a clear technical design plan?

Turning vague ideas into clear design plans requires progressive clarification to define goals and constraints, followed by comparing multiple solution approaches to select a sensible implementation direction before coding begins.

What is the best way to clarify ambiguous software requirements before development?

Clarifying ambiguous software requirements is best achieved through stepwise design review, which breaks the technical design into small sections and validates each part before continuing to ensure implementation direction is fully validated.

How do I compare different technical approaches for early-stage engineering discussions?

Comparing different technical approaches for early-stage engineering involves exploring two to three distinct solutions side-by-side, allowing you to choose a sensible implementation path instead of guessing when product requirements are ambiguous.

Can I generate a handoff-ready design document from a rough feature request?

You can generate a handoff-ready design document from a rough feature request by using progressive clarification and solution exploration to shape the idea into a structured technical brief that flows directly into downstream specification and development work.

When should I not use guided brainstorming for software design exploration?

You should not use guided brainstorming for software design exploration when requirements are already well-defined, the technical direction is clear, or the feature scope is too narrow to require comparing multiple implementation approaches.