# 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.

- Skill: `askaret/feature-spec` (Agent Skill)
- Install (CLI): `npx skillmds@latest add askaret/feature-spec`
- Raw SKILL.md: https://api.skillmd.com/api/skills/askaret/feature-spec/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: askaret (https://skillmd.com/u/askaret)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/askaret/feature-spec

---


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."