stark-ai-de/agent-skills / skills/claude-operations/claude-spec-interviewer
claude-spec-interviewer
VerifiedTurn ambiguous coding requests into verified Claude Code implementation specs. Use when the user wants requirements, an implementation plan, or a spec before coding; include source checks, needed ADRs, and agreed delivery. Do not use for already specified direct implementation or memory cleanup.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.2 KB |
| assets/claude-execution-prompt.md | markdown | 6.1 KB |
| assets/example-repo-refactor.spec.md | markdown | 10.0 KB |
| assets/example-small-task.spec.md | markdown | 3.5 KB |
| assets/spec-template.compact.md | markdown | 1.5 KB |
| assets/spec-template.deep.md | markdown | 3.9 KB |
| assets/spec-template.standard.md | markdown | 3.3 KB |
| references/adr-gate.md | markdown | 2.7 KB |
| references/artifact-destinations.md | markdown | 3.0 KB |
| references/host-adapters.md | markdown | 5.5 KB |
| references/question-bank.md | markdown | 5.0 KB |
| references/rollout-checklist.md | markdown | 2.7 KB |
| references/source-challenge.md | markdown | 2.9 KB |
| references/spec-rubric.md | markdown | 6.5 KB |
| references/workflow-details.md | markdown | 9.0 KB |
references/artifact-destinations.md
View on GitHub# Artifact destinations
Use when selecting delivery and concrete spec/ADR paths. Reuse the request, prior answers and exact write authority; do not restart permission discovery at finalization.
## Discover delivery and paths
1. Default to a repository-owned saved spec; explicit chat-only delivery takes precedence without a persistence question. Carry existing save authority forward and identify the path while interviewing.
2. Use an explicit path first, then a clear repository convention. If neither exists, propose `docs/specs/<kebab-slug>-spec.md`.
3. Inspect public/private placement, directory existence and existing destination content. Raise material ambiguity early or include it in the final checkpoint. Do not interrupt merely to confirm a clear existing convention.
4. Include unapproved directory creation, overwrites, required ADR writes and minimal ADR index updates in the same concrete checkpoint. Previously approved actions do not need another question unless their scope or target state changed.
In this `agent-skills` repository, follow `docs/specs.md`: use the ignored `docs/specs/do-not-publish/` for private, exploratory, sensitive, repository-creation, or not-yet-public specs. Use public `docs/specs/` only after the maintainer explicitly confirms publishability. In other repositories, local conventions take precedence. An intentionally local-only artifact does not require a new sharing question; ask only when an ignored destination conflicts with the requested shared result. Never unignore a path implicitly.
Use lowercase kebab-case names ending in `-spec.md` unless the repository requires another format. Do not add sequential numbers unless the repository does.
## Approve and persist
Follow [workflow-details.md](workflow-details.md): prepare the complete reviewable content, then combine content approval and outstanding concrete write decisions into one positive checkpoint. A mode toggle alone is not approval. Do not overwrite a file merely because the slug matches; inspect its content and reuse only authority that covers that content/state.
Native Plan permits no repository persistence. Keep an approved result pending until actual exit and known write permissions, without asking approval again. During save-only finalization write only the spec, required ADR and minimal convention-required ADR index entry; capture other documentation work in the spec for later implementation. Read back saved artifacts and report actual paths. Explicit chat-only output completes the requested delivery; a blocked requested save remains incomplete.
## ADR destinations and status
Follow the repository's ADR directory, linked representations, template, numbering and index. Keep one durable decision per ADR. Default to `Proposed` unless the maintainer explicitly accepts the reviewed decision. Approval to save a proposed ADR is not decision acceptance. Carry prior acceptance forward when unchanged. Link required ADRs from the spec and block dependent implementation until acceptance.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |