expert-plan

Interview users to produce an auditable Markdown feature specification.

1|Updated Jul 31, 2023
One-click install
npx skills add https://github.com/austintheriot/dotfiles --skill expert-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expert-plan
Source: https://github.com/austintheriot/dotfiles/tree/main/.claude/skills/expert-plan
Command: npx skills add https://github.com/austintheriot/dotfiles --skill expert-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves unclear requirements by driving an iterative, evidence-backed conversation that produces a coherent feature specification before any implementation begins.

Core Features & Use Cases

  • Relentless requirements grilling: Interviews the human question-by-question to reach shared understanding and eliminate hidden assumptions.
  • Expert-lens spec critique: Consults a curated panel (e.g., security, performance, distsys/data, observability) to identify spec-level risks and missing decisions.
  • Iterative convergence loop: Re-grills only what remains uncertain or high-impact, updates a spec artifact each cycle, and surfaces contradictions for human resolution.
  • Spec artifact ownership: Writes and updates a Markdown spec file owned by the user, supporting auditable decision history.

Quick Start

Use the expert-plan skill to create and iteratively refine a feature spec from your ticket, notes, or draft by prompting it to confirm the spec path and then run the grill-and-critique cycles.

Frequently Asked Questions about expert-plan

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

FAQPage Schema
How do I turn fragmented product requirements into a firm feature specification?

To turn fragmented product requirements into a firm feature specification, use an iterative grilling process that interviews stakeholders question-by-question, applies expert critique across domains like security and performance, and writes the evolving design into an auditable Markdown spec artifact.

What is the best way to align a team on feature design before code is written?

The best way to align a team on feature design before code is written is to perform first-principles in-scope checks and surface contradictions through an iterative convergence loop, ensuring a shared understanding is captured in a decision log.

How do I identify missing decisions and spec-level risks in a product plan?

To identify missing decisions and spec-level risks in a product plan, consult a curated specialist roster covering areas like security, performance, and observability to apply expert-lens critique against the evolving design.

Can I use iterative design to resolve hidden assumptions in a feature spec?

Yes, you can use iterative design to resolve hidden assumptions by re-grilling only what remains uncertain or high-impact in each cycle, updating the specification artifact until convergence recommendations are met or you issue a stop command.

When do I need to stop the requirements clarification cycle for a feature spec?

You need to stop the requirements clarification cycle for a feature spec when the iterative convergence loop determines remaining uncertainties are low-impact, or when you explicitly issue a stop command to halt the expert-lens critique process.

Does the expert-plan skill write an auditable decision log for product planning?

Yes, expert-plan writes and updates a Markdown spec artifact owned by the user, which serves as an auditable decision log capturing the history of requirements clarification and design choices for product planning.