origin-grill

Interviews users one question at a time to create or revise repository specs in docs/specs.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/Aki2022/skills --skill origin-grill-aki2022
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: origin-grill
Source: https://github.com/Aki2022/skills/tree/main/origin-grill
Command: npx skills add https://github.com/Aki2022/skills --skill origin-grill-aki2022

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Ambiguous product or feature ideas often jump straight into implementation without a validated specification, leading to rework and misaligned intent. This Skill turns an unclear direction into an approved, stress-tested spec file under docs/specs through a structured one-question-at-a-time interview. ## Core Features & Use Cases - Assumption stress-testing: Challenges every material decision with counterexamples, boundary cases, and failure scenarios before it is recorded. - Incremental spec drafting: Creates or revises docs/specs files from a template, persisting resolved decisions, open questions, and the next question after every answer. - Domain language sharpening: Canonicalizes vague terms and records them in the spec's Domain Language section, surfacing contradictions with existing docs and code. - Use Case: You have a rough idea for a new billing feature. The Skill interviews you about the problem, actors, scope, edge cases, and acceptance criteria, writes a draft spec as decisions resolve, and marks it active only after your explicit approval. ## Quick Start Use origin-grill to interview me one question at a time and turn my rough feature idea into an approved spec in docs/specs.

Frequently Asked Questions about origin-grill

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

FAQPage Schema
How do I turn a vague feature idea into a written spec?

Run a structured interview that asks one decision question per turn, starting with the problem and desired outcome, then actors, scope, edge cases, constraints, and acceptance criteria. Resolved decisions are written into a draft spec file after each answer.

How to stress-test assumptions in a product specification?

Challenge each material decision with a concrete counterexample, boundary case, or failure scenario, and track each branch as open, settled, deferred, or out-of-scope. Stop probing a branch once its outcome cannot change the stated goals or acceptance criteria.

When should I not use a spec interview workflow?

Skip it for mechanical spec edits, typo fixes, read-only summaries, or implementation work after a spec is already settled. The interview process is designed for greenfield ideas and substantive revisions where intent is still ambiguous.

Can the interview resume if a session is interrupted?

Yes. The draft spec keeps an Open Questions section and a single Next Question field, so an interrupted session can resume exactly where it stopped. The spec stays in draft status and implementation must not start from it.

Does the skill implement the feature after the spec is approved?

No. It never starts implementation, creates branches, or creates workstreams. After approval it sets the spec status to active and hands off implementation planning to a separate documentation workflow.