new-feature

Generate linked PRD, SPEC, ADR, and TASK artifacts for new features.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/DarkCodePE/starteria --skill new-feature-darkcodepe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-feature
Source: https://github.com/DarkCodePE/starteria/tree/main
Command: npx skills add https://github.com/DarkCodePE/starteria --skill new-feature-darkcodepe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end scaffolding workflow for a new feature by generating a linked PRD slice, SPEC, ADR references, and TASK breakdowns to accelerate starting work and ensure traceability.

Core Features & Use Cases

  • Automatically generates a PRD slice with user stories in EARS format.
  • Drafts a matching SPEC with architecture overview, API contracts, data models, and acceptance criteria.
  • Produces a set of TASK units that fit within a Claude Code session, with dependencies and session design.
  • Ensures traceability by linking artifacts (PRD → SPEC → ADRs → TASKs).
  • Useful for starting work on any new capability, feature, or user story, enabling rapid sprint kickoff.

Quick Start

Run the New Feature Scaffold skill to initialize a feature scaffold and generate the PRD slice, SPEC, ADR references, and task breakdown.

Frequently Asked Questions about new-feature

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

FAQPage Schema
How do I scaffold a full feature artifact chain for sprint planning?

Scaffold a feature artifact chain by automatically generating a linked PRD slice, SPEC, ADR references, and TASK breakdown to accelerate sprint kickoff and ensure lifecycle traceability. This automation produces ready-to-implement task definitions mapped directly from user stories.

What is the PRD-SPEC-TASK artifact chain used for in agile development?

The PRD-SPEC-TASK artifact chain enforces traceability in agile development by linking product requirements to technical specifications and actionable tasks. This structured linkage ensures clear acceptance criteria and ready-to-implement definitions for lifecycle management.

How do I generate EARS format user stories and matching technical specifications?

Generate EARS format user stories and matching specifications by running an automated feature scaffold that drafts a PRD slice and a SPEC with architecture overviews, API contracts, and data models. This ensures alignment between requirements and technical design.

Can I break down a new feature into task units that fit within a single development session?

Yes, you can break down a new feature into task units designed to fit within a development session. The scaffolding process produces a TASK breakdown complete with dependencies and session design, creating ready-to-implement units mapped to the SPEC.

Does this feature scaffolding workflow require any specific architecture decision records to start?

No specific architecture decision records are required beforehand to start feature scaffolding. The process automatically produces ADR references alongside the SPEC and TASK breakdown, integrating architectural decisions into the traceable artifact chain.