One-click install
npx skills add https://github.com/Flowm/dotfiles --skill grilling-flowm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/Flowm/dotfiles/tree/main/home/.agents/skills/grilling
Command: npx skills add https://github.com/Flowm/dotfiles --skill grilling-flowm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unvalidated plans often contain unaddressed gaps, misaligned stakeholder assumptions, and unresolved cross-decision dependencies that lead to costly implementation failures and rework later in the development process.

Core Features & Use Cases

  • Iterative Plan Interrogation: Walks through every branch of a plan or design, asking one targeted question at a time to resolve dependencies between decisions sequentially.
  • Guided Decision Support: Provides a recommended answer for each question to speed up alignment and reduce decision fatigue.
  • Use Case: Use this skill when you have a new product feature roadmap and want to catch resource gaps, edge cases, and stakeholder misalignment before allocating engineering time to build it.

Quick Start

Use the grilling skill to stress-test my plan for rolling out the new user notification system.

Frequently Asked Questions about grilling

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

FAQPage Schema
How do I stress-test a product plan to catch gaps before build?

Stress-test a product plan by applying iterative interrogation to resolve cross-decision dependencies and misaligned assumptions. This process walks through every branch sequentially, asking one targeted question at a time with recommended answers to confirm shared understanding before execution.

What is the best way to validate stakeholder alignment on a new feature roadmap?

Validate stakeholder alignment through pre-build plan review using iterative questioning. By sequentially addressing each decision branch and providing recommended answer options, you eliminate unresolved dependencies and confirm shared understanding across product, engineering, and project stakeholders.

How does iterative questioning resolve cross-decision dependencies in project planning?

Iterative questioning resolves cross-decision dependencies by walking through every plan branch sequentially. It asks one targeted question at a time and provides recommended answers, ensuring sequential resolution of decision dependencies to prevent implementation failures.

Can I use a pre-build review to prevent rework on engineering plans?

Pre-build review eliminates unaddressed gaps and misaligned stakeholder assumptions that cause rework. By stress-testing designs and resolving cross-decision dependencies sequentially before allocating engineering time, you prevent costly implementation failures.

What types of plans are suitable for design stress-testing?

Design stress-testing suits product, engineering, and project planning scenarios. It applies to pre-build plan review workflows where you need to catch resource gaps, edge cases, and stakeholder misalignment before execution begins.

Do I need to prepare specific documentation for a pre-build plan review?

Pre-build plan review requires your product feature roadmap or design documentation. The skill interacts with your plan iteratively, asking one targeted question at a time and providing recommended answers to resolve dependencies sequentially.