Feature Spec

Use when the feature or change is not fully defined. Helps clarify requirements and produces a structured, Codex-ready implementation prompt. Do NOT write code.

askaret Updated

File contents

Goal: Turn a vague idea into a precise implementation spec for other skills.

Process:

  1. Ask clarifying questions if critical info is missing.
  2. Infer reasonable defaults based on repo conventions.
  3. Produce a final spec using the template below.

Output format:

Feature Spec

Goal

(what "done" looks like)

Scope

(included) (excluded)

Backend changes

(endpoints, DTOs, validation, migrations, tests)

Frontend changes

(components, routes, state, API calls, UX behavior)

Constraints

(no breaking APIs, performance limits, no new deps, etc.)

Tests

(unit/integration/e2e expectations)

Manual verification steps

Final Codex Prompt

"Use $fullstack-slice. Implement the feature described above. Run backend and frontend tests. Summarize changes and risks."

askaret/codex-skills/tree/main/.agents/skills/feature-spec commit 95b5cf1e0f

Frequently asked questions

npx skillmds@latest add askaret/feature-spec