feature-plan

Generate structured Markdown feature plans from user goals and requirements.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Suniljit/personal-toolkit --skill feature-plan-suniljit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-plan
Source: https://github.com/Suniljit/personal-toolkit/tree/main/.opencode/skills/feature-plan
Command: npx skills add https://github.com/Suniljit/personal-toolkit --skill feature-plan-suniljit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams plan features or fixes before building, turning vague ideas into a clear, executable plan that guides development and reduces rework.

Core Features & Use Cases

  • Guided grilling: Probes requirements step-by-step to surface dependencies, risks, and success criteria.
  • Structured plan generation: Produces a concise, agent-ready Markdown plan with sections for summary, decisions, architecture, files, implementation, testing, and risks.
  • Flexible entry points: Works with or without a formal ticket or feature brief, saving the plan to a location you specify.

Quick Start

Tell me the feature or ticket details and where to save the plan, and I’ll generate a structured Markdown plan after grilling the requirements.

Frequently Asked Questions about feature-plan

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

FAQPage Schema
How do I plan feature work end-to-end before coding?

Yes, structured feature planning works for both ticket-based briefs and standalone feature requests, saving the generated executable plan to a user-specified location without requiring a formal ticket.

What is the best way to turn vague feature requirements into an executable plan?

Structured feature planning reduces development rework by probing requirements step-by-step to surface dependencies, risks, and success criteria before generating a concise, agent-ready Markdown plan.

How do I grill requirements to document architecture and risk handling?

You grill requirements by probing the feature goals step-by-step to surface dependencies and risks, which then enforces a strict plan format documenting architecture, files, implementation, testing, and risk handling.

What sections are included in a structured feature plan document?

A structured feature plan document includes strict sections for summary, decisions, architecture, files, implementation, testing, and risk handling to guide development end-to-end.

Do I need a formal ticket to generate a structured feature plan?

No, you do not need a formal ticket to generate a structured feature plan, because the planning process accepts flexible entry points and works with standalone feature requests.