Feature Planner

VerifiedSafe

Turn a vague feature request into a concrete plan with scope, constraints, acceptance criteria, and risks.

Sby Skills Guide Bot
DevelopmentIntermediate
007/23/2026
Claude Code
#feature-planning#requirements#acceptance-criteria#risk-analysis

Recommended for

Our review

Turns a vague feature request into a structured implementation plan with goals, constraints, and acceptance criteria.

Strengths

  • Clarifies scope and non-goals to prevent scope creep
  • Identifies risks and technical dependencies early
  • Produces testable acceptance criteria
  • Documents open questions for design iteration

Limitations

  • Relies on the quality of the initial request
  • May be overly formal for trivial changes
  • Does not replace a full impact analysis
When to use it

Use this skill before implementing a complex or ambiguous feature to align the team on a shared vision.

When not to use it

Avoid this skill for simple bugs or maintenance tasks that don't require upfront planning.

Security analysis

Safe
Quality score90/100

The skill is purely declarative, guiding the AI to produce a textual plan without any tool execution, file access, or network activity. No security risks are present.

No concerns found

Examples

Plan a new authentication feature
Plan the implementation for adding OAuth2 login to our web app. The feature should support Google and GitHub as providers, and store tokens securely. Existing users can still use email/password.
Scope a dark mode toggle
I want to add a dark mode toggle to the settings page. It should apply system-wide and respect the OS preference by default. Create an implementation plan.
Outline a notification system
Plan a feature: users receive email notifications for new messages. Notifications can be paused per conversation. We use SendGrid. Generate the plan with goals, non-goals, and risks.

name: feature-planner description: Turn a feature request into an implementation-ready plan with scope, constraints, acceptance criteria, and risks.

Goal

Convert an ambiguous feature idea into a concrete plan before implementation.

Workflow

  1. Restate the target outcome in one paragraph.
  2. Separate goals from non-goals.
  3. Identify affected user flows, entry points, and likely files.
  4. List constraints, dependencies, and migration concerns.
  5. Produce acceptance criteria.
  6. Leave unresolved questions as explicit open items.

Output format

Outcome

Goals

Non-goals

Affected areas

Constraints and risks

Acceptance criteria

Open questions

Related skills