new-spec

Scaffold feature specifications and implementation plans with acceptance criteria.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/phanijapps/engram --skill new-spec-phanijapps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-spec
Source: https://github.com/phanijapps/engram/tree/main/.claude/skills/new-spec
Command: npx skills add https://github.com/phanijapps/engram --skill new-spec-phanijapps

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill eliminates ambiguity in feature development by enforcing a contract-first approach, ensuring that every new feature is defined by a precise specification and a verifiable implementation plan before any code is written.

Core Features & Use Cases

  • Spec-Driven Development: Automatically scaffolds spec and plan documents that force clear definitions of objectives, boundaries, and acceptance criteria.
  • Assumption Verification: Mandates a rigorous, evidence-based check of technical, product, and process assumptions to prevent "context poisoning."
  • Contract Enforcement: Integrates with interface-specific authoring skills to ensure that API, event, or schema contracts are defined and linked to the feature spec.

Quick Start

Invoke the new-spec skill to start a feature for user-onboarding and follow the prompts to scaffold the documentation.

Frequently Asked Questions about new-spec

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

FAQPage Schema
How do I standardize feature specifications and implementation plans before writing code?

Standardize feature specifications by enforcing a contract-first approach that scaffolds precise spec and plan documents with clear objectives, verifiable acceptance criteria, and architectural boundaries before development begins.

What is contract-first development and how does it define architectural boundaries?

Contract-first development defines interface contracts, API schemas, and architectural boundaries upfront, ensuring every new feature is governed by a precise specification and verifiable implementation plan before code execution.

How do I verify technical and product assumptions to prevent context poisoning during development?

Verify assumptions by applying an evidence-based check to technical, product, and process assumptions during feature specification, rigorously validating context to prevent context poisoning and ambiguity in implementation plans.

How do I scaffold documentation for new features with present-tense specifications and acceptance criteria?

Scaffold feature documentation by invoking the planning skill, which automatically generates spec and plan documents requiring strict present-tense documentation, clear boundaries, and verifiable acceptance criteria.

Can I link API and event schema contracts to a feature specification for governance?

Link API and event schema contracts to feature specifications through contract enforcement, integrating with interface-specific authoring skills to ensure defined contracts are connected to the feature governance plan.

Does contract-first specification work without external dependencies for local development planning?

Contract-first specification operates with zero external dependencies, scaffolding standalone feature specs and implementation plans directly within a repository to enforce governance and architectural boundaries locally.