Best use case
add-new-feature is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using add-new-feature should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/add-new-feature/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How add-new-feature Compares
| Feature / Agent | add-new-feature | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill provides specific capabilities for your AI agent. See the About section for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Add New Feature (SAM Workflow)
You MUST convert the user's request into **durable SAM artifacts** under the repo:
- `plan/feature-context-{slug}.md` (discovery)
- `plan/codebase/{FOCUS}.md` (optional, analysis)
- `plan/architect-{slug}.md` (architecture/design spec)
- `plan/tasks-{N}-{slug}.md` (executable task plan with Agents, deps, and verification)
<feature_request>
$ARGUMENTS
</feature_request>
---
## Orchestrator Discipline
You are an orchestrator. You coordinate work across specialized agents. Prefer delegating discovery and analysis.
---
## Phase 1: Discovery (feature-researcher)
Delegate to `feature-researcher` to produce `plan/feature-context-{slug}.md` and questions for resolution.
---
## Phase 2: Codebase Analysis (codebase-analyzer)
If helpful, delegate to `codebase-analyzer` for one or more focus areas:
- patterns
- architecture
- testing
- conventions
Outputs go to `plan/codebase/`.
---
## Phase 3: Architecture Spec (python-cli-design-spec)
Delegate to `python-cli-design-spec` to write `plan/architect-{slug}.md` based on:
- the feature context doc
- codebase analysis docs (if created)
- existing repo constraints (`CLAUDE.md`, `pyproject.toml`, etc.)
---
## Phase 4: Task Decomposition (swarm-task-planner)
Delegate to `swarm-task-planner` to:
- create `plan/tasks-{N}-{slug}.md`
- ensure every task has:
- **Status**, **Dependencies**, **Priority**, **Complexity**, **Agent**
- Acceptance Criteria (3+)
- Verification Steps (3+)
---
## Phase 5: Plan Validation Gate (plan-validator)
Delegate to `plan-validator`. If it returns `BLOCKED`, do not proceed.
---
## Phase 6: Context Manifest (context-gathering)
Delegate to `context-gathering` with the task file path. It must insert a `## Context Manifest` into the task file.
---
## Success Outcome
When all phases complete, provide the user:
- the feature slug
- the task file path
- next step: run the `implement-feature` skill with the slug or task file pathRelated Skills
Create Jira Feature
Implementation guide for creating Jira features representing strategic objectives and market problems
create-feature
Creates Features following the T-Minus-15 process template. Features represent significant deliverables that contain multiple User Stories. Includes proper metadata, MoSCoW prioritization, effort estimates, deliverables, and benefit hypothesis.
create-feature-branch
Create properly named feature branch from development with remote tracking, following WescoBar naming conventions and git best practices
correlation-methylation-epiFeatures
This skill provides a complete pipeline for integrating CpG methylation data with chromatin features such as ATAC-seq signal, H3K27ac, H3K4me3, or other histone marks/TF signals.
copilot-customization-features
Use when creating or modifying any GitHub Copilot customization features in VS Code, including custom instructions, AGENTS.md, agent skills, prompt files, custom agents, agent hooks, or AGENTS.md files. Helps select the correct feature type and create, review, or modify it for optimal performance.
configure-feature-flags
Check and configure feature flag infrastructure (OpenFeature + providers)
backend-development-feature-development
Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.
alto-feature-setup
Use when starting a new feature - running /alto-feature-setup, updating objective.md, or running alto-new-run. Interactive workflow for feature initialization.
ai-feature-template
Create new AI-powered features using xAI Grok. Use when user mentions "new AI feature", "add Grok", "create prompt", "AI analysis", or "generate with AI".
feature-docs
[Documentation] Create or update business feature documentation in docs/business-features/{Module}/. Generates comprehensive 26-section docs with verified code evidence and AI companion files. Triggers on: feature docs, business feature documentation, module documentation, document feature, update feature docs, ai companion, ai context file, quick feature docs, feature readme, single file docs, verified documentation.
Feature Flag Strategy
Design and manage feature flag lifecycles for safe, gradual rollouts
team-feature
Launch Agent Team for feature implementation with review gates (coders + specialized reviewers + tech lead)