Skill

feature-workflow

AI-driven feature development workflow. USE THIS SKILL when the user requests a new feature, significant change, or says "new feature", "add feature", "implement X", "build X", or similar. Guides AI agents through 3 phases: DECIDE (ADR), PLAN (implementation specs), BUILD (execute & track). Ensures architectural consistency, traceability, and quality across any tech stack. Also trigger when user mentions "ADR", "architecture decision", "implementation plan", or "feature workflow".

Install

npx claudepluginhub slyk/toopro-code-style --plugin feature-workflow

Tool Access

This skill uses the workspace's default tool permissions.

Preview

This skill defines the **3-phase methodology** for developing new features using AI agents.

Supporting Assets

references/templates/adr-template.mdreferences/templates/architecture-template.mdreferences/templates/backend-implementation-template.mdreferences/templates/frontend-implementation-template.mdreferences/templates/implementation-plan-template.mdreferences/templates/progress-template.mdreferences/templates/shared-implementation-template.mdreferences/workflow.md

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 16, 2026

Actions

View Source View Plugin View on GitHub View README

feature-workflow

Feature Development Workflow

This skill defines the 3-phase methodology for developing new features using AI agents. Every new feature or significant change MUST follow this workflow.

Read the full workflow guide: references/workflow.md

Quick Reference

Phase

Output

Gate

DECIDE

_ai/decisions/ADR-{N}-{slug}.md

User approval required

PLAN

_ai/implementations/{slug}/ folder

User approval required

BUILD

Code + progress.md updates

Tests pass

When Triggered

Read references/workflow.md for the complete process

Check _ai/decisions/ for existing ADRs (to determine next ADR number)

Check _ai/knowledge-base/ for relevant patterns and guides about existing subsystems

Check project's CLAUDE.md or AGENTS.md for architecture info, lib structure, and conventions

Follow the 3 phases with user approval gates between each

Templates

All templates are in references/templates/:

Template

When to use

adr-template.md

Phase 1: Create architecture decision record

implementation-plan-template.md

Phase 2: Main plan with scope and acceptance criteria

backend-implementation-template.md

Phase 2: Backend/API changes (optional, use when feature has backend work)

frontend-implementation-template.md

Phase 2: Frontend/UI changes (optional, use when feature has frontend work)

shared-implementation-template.md

Phase 2: Shared libs/types (optional, use when feature affects shared code)

progress-template.md

Phase 2: Task checklist for tracking build progress

architecture-template.md

Post-build: Update or create architecture docs

Critical Rules

Never skip phases. Even small features need at least a lightweight ADR.

Never start coding without an approved plan. The plan is the contract.

Always update progress.md as you complete tasks during BUILD.

Always update architecture docs after significant changes.

Always check knowledge-base before starting — it may contain patterns for similar work.

Agents MUST read their implementation spec before writing code.

Feature Development Workflow

This skill defines the 3-phase methodology for developing new features using AI agents. Every new feature or significant change MUST follow this workflow.

Read the full workflow guide: references/workflow.md

Quick Reference

Phase	Output	Gate
DECIDE	`_ai/decisions/ADR-{N}-{slug}.md`	User approval required
PLAN	`_ai/implementations/{slug}/` folder	User approval required
BUILD	Code + `progress.md` updates	Tests pass

When Triggered

Read references/workflow.md for the complete process
Check _ai/decisions/ for existing ADRs (to determine next ADR number)
Check _ai/knowledge-base/ for relevant patterns and guides about existing subsystems
Check project's CLAUDE.md or AGENTS.md for architecture info, lib structure, and conventions
Follow the 3 phases with user approval gates between each

Templates

All templates are in references/templates/:

Template	When to use
`adr-template.md`	Phase 1: Create architecture decision record
`implementation-plan-template.md`	Phase 2: Main plan with scope and acceptance criteria
`backend-implementation-template.md`	Phase 2: Backend/API changes (optional, use when feature has backend work)
`frontend-implementation-template.md`	Phase 2: Frontend/UI changes (optional, use when feature has frontend work)
`shared-implementation-template.md`	Phase 2: Shared libs/types (optional, use when feature affects shared code)
`progress-template.md`	Phase 2: Task checklist for tracking build progress
`architecture-template.md`	Post-build: Update or create architecture docs

Critical Rules

Never skip phases. Even small features need at least a lightweight ADR.
Never start coding without an approved plan. The plan is the contract.
Always update progress.md as you complete tasks during BUILD.
Always update architecture docs after significant changes.
Always check knowledge-base before starting — it may contain patterns for similar work.
Agents MUST read their implementation spec before writing code.