AgentSkillsCN

shep-kit:new-feature

在启动任何新功能、新特性或功能增强时使用此技能。触发条件包括“新功能”、“开始开发”、“添加功能”、“实现 X”，或显式调用 /shep-kit:new-feature。创建规格分支，并搭建规格目录。

SKILL.md
--- frontmatter
name: shep-kit:new-feature
description: Use when starting any new feature, functionality, or enhancement. Triggers include "new feature", "start developing", "add functionality", "implement X", or explicit /shep-kit:new-feature invocation. Creates spec branch and scaffolds specification directory.

Create New Feature Specification

Start spec-driven development by creating a feature branch and specification directory.

Full workflow guide: docs/development/spec-driven-workflow.md

Phase Lifecycle

code
Requirements → Research → Planning → Implementation → Complete
    ↓             ↓           ↓            ↓            ↓
 spec.md     research.md   plan.md     tasks.md    all files

CRITICAL: Each phase MUST update the Phase status field before proceeding.

Workflow

1. Gather Minimal Input

Ask the user for:

  • •Feature name (kebab-case, e.g., user-authentication)
  • •One-liner description (brief summary)

2. Create Branch

bash
# Determine next number
NEXT_NUM=$(ls -d specs/[0-9][0-9][0-9]-* 2>/dev/null | wc -l | xargs printf "%03d" $(($ + 1)))
# If no specs exist, use 001
[ -z "$NEXT_NUM" ] && NEXT_NUM="001"

# Create branch from main
git checkout main && git pull
git checkout -b "feat/${NEXT_NUM}-${FEATURE_NAME}"

3. Run Init Script

Execute the scaffolding script:

bash
.claude/skills/shep-kit:new-feature/scripts/init-feature.sh <NNN> <feature-name>

This creates specs/NNN-feature-name/ with all template files, including feature.yaml.

4. Analyze Context

Before filling the spec, analyze:

  • •Existing specs: Read specs/*/spec.md to understand feature landscape and discover dependencies
  • •Codebase: Identify affected areas, patterns, existing implementations
  • •Cross-reference: Infer dependencies, impact areas, size estimate

5. Propose Spec Content

Fill the template placeholders with inferred values:

  • •Problem statement (from user description + context)
  • •Success criteria (inferred from scope)
  • •Affected areas with impact levels (from codebase analysis)
  • •Dependencies on other features (from existing specs)
  • •Size estimate with reasoning (S/M/L/XL)
  • •Open questions (gaps identified during analysis)

Present the proposed spec to the user for review.

6. User Confirms/Adjusts

Allow the user to:

  • •Approve the proposed spec
  • •Modify any inferred values
  • •Add missing context or requirements

7. Write Spec & Update feature.yaml

bash
# Update spec.md with confirmed content
# feature.yaml already created by init script with initial state:
#   - lifecycle: "research"
#   - phase: "research"
#   - checkpoint: "feature-created"
# See: docs/development/feature-yaml-protocol.md for details

# Stage and commit
git add specs/NNN-feature-name/
git commit -m "feat(specs): add NNN-feature-name specification"

feature.yaml Status: Already initialized by init script. No manual updates needed at this stage.

8. Next Steps

Inform the user:

Spec created on feat/NNN-feature-name! Next: /shep-kit:research to analyze technical approach.

Open Questions Policy

CRITICAL: Open questions in spec.md MUST be resolved before /shep-kit:research.

  • •If questions are identified, list them with - [ ] checkbox format
  • •User must confirm answers or mark "None - requirements are clear"
  • •Research phase will REFUSE to proceed if unchecked open questions exist

Key Principles

  • •Branch first: All spec work happens on the feature branch
  • •Infer, don't interrogate: Analyze codebase to propose smart defaults
  • •Dependencies from specs: Scan existing specs/*/spec.md for relationships
  • •User confirms: Always get approval before writing files
  • •Open questions block progress: Never proceed with unresolved questions

Template Location

Templates are in: .claude/skills/shep-kit:new-feature/templates/

Templates include:

  • •spec.md - Feature specification
  • •research.md - Technical decisions
  • •plan.md - Implementation strategy
  • •tasks.md - Task breakdown
  • •data-model.md - Domain models
  • •feature.yaml - Status tracking (NEW)

feature.yaml Protocol

All shep-kit skills update feature.yaml as work progresses.

Reference: docs/development/feature-yaml-protocol.md

This skill's responsibility:

  • •Create initial feature.yaml with:
    • •lifecycle: "research"
    • •phase: "research"
    • •Checkpoint: "feature-created"

Example

See: .claude/skills/shep-kit:new-feature/examples/001-sample-feature/