Skip to content
Skill

new-feature

by camalus

AI Summary

Guide the practitioner through creating a complete, linked artifact chain for a new feature: PRD slice → Technical Specification → ADR identification → Task breakdown. Ask the practitioner: 1. What is the feature name? (5 words max for the title)

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "new-feature" skill in my project.

Please run this command in my terminal:
# Install skill into your project
mkdir -p .claude/skills/BHIL-AI-First-Development-Toolkit && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/BHIL-AI-First-Development-Toolkit/SKILL.md "https://raw.githubusercontent.com/camalus/BHIL-AI-First-Development-Toolkit/main/SKILL.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

Create a complete feature artifact scaffold — PRD slice, technical spec, and task breakdown. Use when starting work on any new feature, user story, or capability. Triggers on phrases like 'new feature', 'create a PRD for', 'start work on', 'scaffold a feature'.

Step 1: Gather requirements (ask these questions before creating any files)

Ask the practitioner: • What is the feature name? (5 words max for the title) • What problem does it solve? (one sentence, no solution hints) • Who is the user? (be specific — not "users," e.g., "authenticated enterprise customers") • What does success look like? (ask for at least one quantified metric) • What is explicitly OUT of scope? • Is this feature AI-native (LLM-powered)? If yes, which capability? Do not proceed until all five questions are answered.

Purpose

Guide the practitioner through creating a complete, linked artifact chain for a new feature: PRD slice → Technical Specification → ADR identification → Task breakdown.

Step 2: Determine the next available ID

Run: `bash ls project/.sdlc/specs/PRD-*.md 2>/dev/null | tail -1 ` The next PRD ID is one higher. If no PRDs exist, start at PRD-001. Use the same number for SPEC-NNN.

Step 3: Create the PRD slice

Copy templates/prd/PRD-TEMPLATE.md to project/.sdlc/specs/PRD-NNN-[kebab-feature-name].md. Fill in: • frontmatter: id, title, date (today), sprint (current sprint from project/sprints/ folder name) • Problem statement: one sentence from practitioner's answer to Q2 • User stories: 2–3 EARS-format stories capturing the practitioner's feature description • Success metrics: quantified from practitioner's answer to Q4 • Out of scope: from practitioner's answer to Q5 Present the draft PRD to the practitioner for review before proceeding.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 24d ago
Active
Adoption100+ stars on GitHub
126 ★ · Growing
DocsREADME + description
Well-documented

GitHub Signals

Stars126
Forks24
Issues4
Updated24d ago
View on GitHub
No License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code