stark-ai-de/agent-skills / plugins/stark-ai-developer/skills/codex-spec-interviewer
codex-spec-interviewer
VerifiedTurn ambiguous coding requests into verified Codex 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.7 KB |
| agents/openai.yaml | config | 470 B |
| assets/codex-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/openai-icon.png | binary | 32.8 KB |
| assets/product-planning-work-item.md | markdown | 2.6 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 | 8.7 KB |
| references/product-planning-handoffs.md | markdown | 2.2 KB |
| references/question-bank.md | markdown | 4.8 KB |
| references/rollout-checklist.md | markdown | 2.7 KB |
| references/source-challenge.md | markdown | 2.5 KB |
| references/spec-rubric.md | markdown | 6.5 KB |
| references/workflow-details.md | markdown | 9.0 KB |
references/adr-gate.md
View on GitHub# ADR Gate
Use this gate before finalizing the implementation spec. ADRs are for durable architecture and repo-level decisions, not feature notes.
## Create or Draft an ADR When
The spec depends on a new, changed, or superseded decision about:
- package, module, service, or ownership boundaries,
- dependency direction or shared abstraction policy,
- runtime, framework, storage, queue, or external service choice,
- public/shared API contracts,
- data ownership, schema, migration, or compatibility strategy,
- auth, security, permission, or privacy model,
- repo-wide validation, build, deployment, publishing, or release policy,
- replacing or superseding an existing ADR.
## Do Not Create an ADR For
- feature-specific behavior,
- UI copy, layout, or interaction details,
- one-off implementation choices under existing architecture,
- routine refactors that preserve current boundaries,
- test cases, validation commands, or rollout checklist items,
- temporary experiments or prototypes.
## Gate Output
Include this result before the final spec:
```md
## ADR gate
- ADR required: yes/no/unresolved
- Reason:
- Existing ADRs consulted:
- New ADR draft:
- Supersedes:
- Implementation blocked until ADR accepted: yes/no
```
## If ADR Is Required
1. Draft exactly one architectural decision per ADR.
2. Use the repository ADR template and required linked representations; do not impose a numeric word or section limit.
3. Mark status as `Proposed` unless the maintainer explicitly accepts the reviewed decision. Permission to save a proposed ADR is distinct from accepting its decision; preserve prior acceptance when unchanged.
4. Use the repo ADR filename pattern. If no pattern exists, use `NNNN-kebab-title.md` with the next sequential number.
5. Resolve missing ADR directories in the same concrete final checkpoint, reusing earlier directory-creation authority.
6. Persist the ADR when required and report its path. While native Plan mode is active, defer this write to the save-only continuation. During persistence, update the repository's existing ADR index when its convention requires one; treat that minimal entry as part of ADR persistence, not unrelated documentation.
7. Reference the ADR from the implementation spec.
8. If the spec depends on ADR acceptance, mark implementation as blocked or phased.
## Spec Linkage
The final spec should include an `Architectural decisions` section:
- `ADR required: no` for feature-only work.
- `ADR draft: <title>` when the decision is proposed but not saved.
- `ADR path: docs/adrs/NNNN-title.md` when the ADR exists.
- `Implements: ADR-XXXX` when the spec implements an accepted decision.
Do not re-litigate accepted ADRs during implementation unless repo reality or current sources contradict them.
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: 471k | Updated | Claude CodeCodex | Verified | 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 |