new-spec

Creates a feature spec and implementation plan with acceptance criteria before coding.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill new-spec-eugenelim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-spec
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/.agents/skills/new-spec
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill new-spec-eugenelim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill turns a rough feature idea into a disciplined, reviewable spec before implementation starts. It helps teams define what done means, surface assumptions early, and keep the implementation aligned with one clear source of truth.

Core Features & Use Cases

  • Feature Spec Creation: Scaffolds a new feature spec and plan under docs/specs for a specific product idea.
  • Assumption Surfacing: Forces technical, product, and process assumptions to be checked before the spec body is written.
  • Contract-Aware Planning: Detects interface surfaces, links the right contract location, and prepares the plan around it when needed.
  • Guardrailed Execution: Requires boundaries, testing strategy, acceptance criteria, and review discipline so agents do not drift.
  • Use Case: A product manager or engineer uses it to start a new feature with a clear contract, testable scope, and implementation plan.

Quick Start

Ask the agent to write a new feature spec for your idea, and it will scaffold the spec and plan, surface assumptions, and wait for confirmation before filling in the contract and acceptance criteria.

Frequently Asked Questions about new-spec

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

FAQPage Schema
How do I write a feature spec with acceptance criteria before coding?

Feature spec creation scaffolds a new spec and plan under docs/specs, forces assumption surfacing, defines boundaries, and writes acceptance criteria before any coding begins.

What is assumption surfacing in feature planning?

Assumption surfacing in feature planning forces technical, product, and process assumptions to be checked before the spec body is written, preventing drift during implementation.

How do I create an implementation plan from a rough product idea?

Creating an implementation plan from a product idea involves scaffolding a spec, detecting interface surfaces to link contract locations, and generating a structured plan with boundaries and a testing strategy.

Does contract-aware planning work for new product features without existing APIs?

Contract-aware planning detects interface surfaces, links the right contract location, and prepares the plan around it, applicable to new product features needing boundaries defined before coding.

Why should I define acceptance criteria before implementation starts?

Defining acceptance criteria before implementation starts ensures teams establish what done means, maintain review discipline, and prevent agents from drifting away from the original feature spec.

What's the best way to turn feature ideas into disciplined specs?

The best way to turn feature ideas into disciplined specs is applying a workflow requiring spec scaffolding, contract detection, and plan generation to maintain a single reviewable source of truth.