feature-dev-next

Orchestrate stage-based feature development with Quick, Standard, and Deep presets.

5|Updated Mar 30, 2026

Search Tags:#planning #architecture #workflows #presets #design-review #feature-development #log-decisions

Ready to run

npx skills add https://github.com/kenlck/skills --skill feature-dev-next

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-dev-next
Source: https://github.com/kenlck/skills/tree/main/ken-swe/skills/feature-dev-next
Command: npx skills add https://github.com/kenlck/skills --skill feature-dev-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured, stage-based feature development guided by three presets (Quick / Standard / Deep) to fit scope and risk.

Core Features & Use Cases

Three presets to scope work from quick tweaks to complex modules.
Stage-driven workflow with discovery, architecture planning, implementation, and review.
Optional logging of decisions to plans/ for traceability and onboarding.

Quick Start

Use /ken-swe:feature-dev-next add a notifications panel to start a Standard workflow with default settings.

Frequently Asked Questions about feature-dev-next

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

FAQPage Schema

How do I structure feature development workflows for non-trivial features?▼

Feature development workflows for non-trivial features are structured using stage-driven processes that guide discovery, architecture planning, implementation, and review. This approach uses explicit user approvals before proceeding to implementation to ensure right-sized scoping.

What is the best way to scope feature development work based on risk?▼

Scoping feature development based on risk is best handled using three presets: Quick, Standard, and Deep. These presets fit the scope and risk of work from quick tweaks to complex modules, ensuring the workflow matches the complexity of the feature.

How do I log decisions during architecture planning for traceability?▼

To log decisions during architecture planning for traceability, enable log mode within the feature development workflow. This automatically records decisions to the plans/ directory, capturing the reasoning needed for onboarding and future reference.

Can I use a stage-driven workflow for quick tweaks and complex modules?▼

Yes, a stage-driven workflow can be used for both quick tweaks and complex modules by selecting the appropriate preset. The Quick preset handles minor adjustments while the Deep preset manages complex modules requiring full discovery and architecture planning.

Does feature development require explicit approvals before implementation?▼

Yes, feature development requires explicit user approvals to proceed to Stage 4, which is the implementation phase. This ensures that discovery and architecture planning are validated before coding begins, reducing risk in non-trivial features.