Drill spec
Interview the user relentlessly about a plan, spec, or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "drill the spec" or "drill the plan".From its SKILL.md
npx -y skills add Unique-Divine/jiyuu --skill drill-specAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 261 tokens by cl100k_base, as published. Nobody here has run it
Interview me about a plan, spec, or design until we reach shared understanding. Ask direct questions that resolve concrete decisions, ambiguities, risks, and edge cases. For each question, provide your recommended answer.
-
Ask up to five questions per turn. Ask fewer when a single answer blocks the next useful question. Ask in the chat, not with the question tool.
-
If a question can be answered by exploring the codebase, explore the codebase instead.
-
Record decisions as the discussion progresses. If the user is working from an existing spec, plan, issue, or design document, write resolved answers back into that document iteratively. If there is no obvious document, create or propose a short notes/spec file.
-
When recording implementation decisions, add or update a
## Implsection. Use concise logical flows where they make the design easier to execute:input or trigger -> state read/write -> validation -> result -
When recording an answer, capture the decision, rationale, relevant codebase or operational context, and important caveats. Use checkbox sub-bullets only for unresolved work, decisions, or tests.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.