feature-spec

Transform vague feature ideas into Codex-ready implementation specs.

Updated Feb 18, 2026

Search Tags:#template #specification #requirements #clarification #product-management #feature-spec

Ready to run

npx skills add https://github.com/askaret/codex-skills --skill feature-spec-askaret

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/askaret/codex-skills/tree/main/.agents/skills/feature-spec
Command: npx skills add https://github.com/askaret/codex-skills --skill feature-spec-askaret

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague feature ideas into precise implementation specs suitable for development, reducing ambiguity and rework.

Core Features & Use Cases

Clarify requirements with focused questions to fill gaps.
Infer reasonable defaults based on repository conventions.
Produce a final spec using the template that includes Goal, Scope, Backend changes, Frontend changes, tests, and a Codex prompt.

Quick Start

Provide a complete feature spec for a vague idea by applying the template and generating the required sections.

Frequently Asked Questions about feature-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn vague feature ideas into precise implementation specs?▼

To turn vague feature ideas into precise implementation specs, you use a clarification process that asks focused questions to fill gaps and infers reasonable defaults from repository conventions. This produces a complete spec covering goals, scope, backend changes, frontend changes, and tests.

What is the best way to write a feature specification when product requirements are incomplete?▼

Writing a feature specification with incomplete product requirements involves applying a structured template to extract goals and scope. The process clarifies ambiguous details through targeted questions and generates a final Codex-ready prompt to bridge any remaining gaps.

Does generating a feature spec work without existing repository conventions?▼

Generating a feature spec does not require existing repository conventions. The specification process can infer reasonable defaults to fill gaps, but providing repository context helps produce more precise backend and frontend change descriptions for the final implementation.

How to structure a Codex-ready implementation spec for a new product feature?▼

To structure a Codex-ready implementation spec, you apply a template that extracts the feature goal and scope. The output includes specific backend changes, frontend changes, required tests, and a final Codex prompt to guide development.

What sections are needed for a complete feature specification template?▼

A complete feature specification template requires sections for the Goal, Scope, Backend changes, Frontend changes, and tests. It also includes a final Codex prompt to ensure the specification is ready for precise development execution.