aaroncharrier Interview Prompt Builder
Use this skill after interview-engine has produced interview_output.json. The snapshot is the source of truth for prompt generation.
Input Contract
- source:
.interview-engine/session-<yyyy-MM-dd_HH-mm-ss>/interview_output.json
Workflow
- You are an expert at writing Codex prompts.
- Use
Read-OutputJson.ps1to read the session'sinterview_output.json. - Generate the
prompt-<yyyy-MM-dd_HH-mm-ss>.md
Guardrails
- Do not synthesize missing requirements from the original request when the snapshot is incomplete.
- Do not read anything excpt the
interview_output.jsonfile.
Output Contract
interview-engine/session-<yyyy-MM-dd_HH-mm-ss>/prompt-<yyyy-MM-dd_HH-mm-ss>.md
Prompt composition
Include:
- Objective Context
- Why this exists
- What problem we are solving
- Why it matters downstream
- Artifact Contract
- File type
- Naming
- Schema or structure
- Storage location
- Input Contract
- Allowed inputs
- Disallowed assumptions
- Data boundaries
- Constraints and Invariants
- Hard rules
- Formatting rules
- Naming rules
- Idempotency requirements
- Execution Model
- Step ordering
- Required checks
- Deterministic vs exploratory behavior
- State and Memory Model
- What persists
- What is written to disk
- What is ephemeral
- Decomposition Strategy
- Subtasks
- Boundaries between steps
- No cross-responsibility rules
- Validation Criteria
- Structural validation
- Logical validation
- Edge cases
- Test Cases and Examples
- Use sparingly
- Known good inputs and outputs
- Anti-patterns
- Failure Modes and Recovery Rules
- What to do if input is incomplete
- What to do if constraints conflict
- When to stop vs proceed
- Scope Boundaries
- No extra features
- No assumption expansion
- No format drift
- Output Formatting Contract
- Exact structure
- Ordering rules
- Required and optional fields
- Tooling and Execution Interface
- Scripts to call
- File operations allowed
- No direct inline generation when a file-based workflow is required
- Token Efficiency Strategy
- Avoid duplication
- Reference instead of restating
- Prefer schemas over prose
- Determinism Strategy
- No randomness
- Stable ordering
- Explicit defaults
- Integration Context
- Upstream dependencies
- Downstream consumers
- Interface expectations
- Termination Criteria
- All files written
- Validations passed
- No pending ambiguity
Do not:
- invent missing answers
- drop answered context
- hide contradictions
- broaden the task beyond the interview result
Style
- Keep the main prompt concise and actionable.
- Preserve the session's terminology.
- Make the prompt ready to paste into the next Codex stage or agent.