Answer a design or feasibility question with explicitly throwaway spike code — never committed, findings recorded in the diary or an ADR draft. Use when a decision is blocked on "would X even work?" (library capability, API behavior, performance shape). Not for building features — that's /tdd via /implement.
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
/grill-with-docs resolves requirement uncertainty; this skill resolves feasibility uncertainty. The output is an answer, not code. Shared invariant §1 names it directly: feasibility questions are answered by a throwaway spike outside the production tree, never by speculative production code that "we might keep".
id attribute on block nodes through a serialize round-trip: true/false?"). If you can't phrase the question, you're not ready to spike.$TMPDIR), never a path under the project, so it cannot be committed by accident. It may add whatever dependencies it likes there; the repo's dependency policy (constitution/local-engineering.md) does not apply to throwaway dirs.docs/diary.md as a dated entry — or into the relevant ADR draft when the spike settles a decision under /grill-with-docs. Cite versions of anything probed (library, API, service) since answers rot./implement + /tdd. Copying spike code into the repo skips the test-first contract and imports every hardcoded shortcut with it.sh scripts/trace.sh emit kind=spike.verdict [subject=<prd:#N or ticket:#N, when the question came from one>] outcome=true|false|inconclusive --blob <file> data.question='<the question, one line>' reason='<the verdict, with the versions probed, one line>' || :. The trace is written here and never read (the kit's ADR-0008); unconfigured, the call is a silent no-op. Then delete the spike dir, and report: question → verdict → what it unblocks.agranado2k/agentic-sdlc
0f5671d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.