new-feature

Generate PRD, SPEC, and task artifacts with traceability IDs.

129|24|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/camalus/BHIL-AI-First-Development-Toolkit --skill new-feature-camalus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-feature
Source: https://github.com/camalus/BHIL-AI-First-Development-Toolkit/tree/main
Command: npx skills add https://github.com/camalus/BHIL-AI-First-Development-Toolkit --skill new-feature-camalus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the initial phase of feature development by generating a complete artifact scaffold—PRD slice, Technical SPEC, and a Task decomposition—ensuring traceability and alignment with templates.

Core Features & Use Cases

  • Automated PRD slice generation anchored to existing PRD templates.
  • Technical SPEC draft outlining architecture, data models, and acceptance criteria.
  • Task decomposition into implementable units with clear dependencies and parallelization hints.
  • Automatic traceability linking PRD → SPEC → ADRs → TASKS to maintain the artifact chain.

Quick Start

Provide the feature name and key details, and the skill will generate the PRD slice, SPEC, and TASK plan.

Frequently Asked Questions about new-feature

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

FAQPage Schema
How do I generate a PRD and technical spec scaffold for a new feature?

To generate a PRD and technical spec scaffold, you provide the feature name, problem statement, and success metrics to produce a traceable artifact chain containing a PRD slice, Technical SPEC, and linked TASK decomposition.

What is the best way to decompose feature requirements into implementable tasks with traceability?

Decomposing feature requirements into tasks with traceability works by linking PRD slices to Technical SPEC drafts and outputting tasks with dependencies and parallelization hints using unique traceability IDs.

How do I maintain traceability between PRDs, SPECs, and ADRs during feature development?

Maintaining traceability between PRDs, SPECs, and ADRs is achieved by automatically generating a linked artifact chain that connects the PRD slice to the SPEC, scopes ADRs, and maps directly to the decomposed TASK units.

What inputs do I need to provide to automate feature artifact scaffold generation?

Automating feature artifact scaffold generation requires the practitioner to input the feature name, problem statement, and success metrics to anchor the PRD slice and technical SPEC draft to the project templates.

Where are generated feature spec artifacts and task plans stored in the project directory?

Generated feature spec artifacts and task plans are stored under the project/.sdlc/specs directory, keeping the PRD slice, SPEC, and linked tasks organized and ready for review and implementation.