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 |
assets/spec-template.standard.md
View on GitHub---
title: "<short human-readable title>"
slug: "<kebab-case-slug>"
artifact_path: "docs/specs/<kebab-case-slug>-spec.md"
mode: "standard"
status: "draft"
owner: "<person-or-team>"
repo: "<repo-name-or-path>"
created: "YYYY-MM-DD"
updated: "YYYY-MM-DD"
source_request: "<original request>"
---
# <title>
## Goal
<clear problem statement, intended outcome, and why this work matters>
## Scope
### In scope
- <bounded work item>
- <bounded work item>
### Non-goals
- <explicit exclusion>
- <explicit exclusion>
## Repo context
- Relevant files/directories:
- Existing abstractions/patterns to preserve:
- Commands and toolchain:
- Related issue/ADR/PR:
- Unspecified facts:
## User-facing behavior
- User story:
- Primary flow:
- Failure/empty/loading states:
- Accessibility/localization/compatibility notes:
## Requirements
### Functional requirements
- WHEN <condition/event>, THE SYSTEM SHALL <expected behavior>.
- WHEN <condition/event>, THE SYSTEM SHALL <expected behavior>.
- IF <error/unwanted behavior>, THEN THE SYSTEM SHALL <expected behavior>.
### Non-functional requirements
- Performance:
- Reliability:
- Security/privacy:
- Observability/logging:
## Design notes
- Preferred implementation approach:
- Reuse before rewrite:
- Data/API/model changes:
- Tradeoffs considered:
- Follow existing repo conventions unless the spec says otherwise.
## Architectural decisions
- ADR required: yes/no/unresolved
- Existing ADRs consulted:
- ADR draft or path:
- Supersedes:
- Implementation blocked until ADR accepted: yes/no
## File plan
### Expected touched areas
- `path/to/file`
- `path/to/dir`
### Expected new files
- `path/to/new-file`
### Areas not to change
- `path/to/keep-stable`
## Execution plan
1. Confirm the current implementation and extension points.
2. Implement the minimal code changes for the happy path.
3. Add or update tests.
4. Handle error/edge states.
5. Run validation commands.
6. Review for regressions and scope creep.
## Source challenge
- Repo evidence checked:
- ADRs/specs checked:
- External docs checked:
- Requirements revised:
- Requirements preserved:
- Preceding ADR/spec work needed:
- ADR gate result:
- Skipped checks and why:
## User verification
- Reviewed revision and approval evidence:
- Approved scope, assumptions, risks and validation:
- Accepted non-blocking questions:
- Approved delivery, paths and concrete write actions:
- ADR decision acceptance, distinct from draft persistence:
## Artifact plan
- Spec path:
- Destination basis: existing convention/suggested/user-provided/declined
- Outstanding write decisions, if any:
- Spec persistence: pending/saved/not requested/blocked
- Existing file overwrite needed: yes/no
- ADR paths:
- ADR persistence: none/pending/saved/not requested/blocked
- ADR index updates needed:
## Validation
```bash
<install-free verification commands>
<lint>
<typecheck>
<unit/integration tests>
```
### Manual checks
- Verify:
- Verify:
- Verify:
## Risks and rollout
- Primary risk:
- Rollback path:
- Migration/backfill needs:
- Feature-flag or phased rollout need: yes/no
## Done when
- [ ] All functional requirements are met
- [ ] Non-goals remain untouched
- [ ] Validation commands pass
- [ ] Manual checks pass
- [ ] Risks and follow-up notes are documented
## Assumptions and open questions
- Assumption:
- Assumption:
- Open question:
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 |