plan-feature

Guide a Socratic discussion to produce a feature plan artifact.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Utchash007/TermTales --skill plan-feature-utchash007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-feature
Source: https://github.com/Utchash007/TermTales/tree/main/.agents/skills/plan-feature
Command: npx skills add https://github.com/Utchash007/TermTales --skill plan-feature-utchash007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-Feature guides a developer through a focused Socratic conversation to uncover requirements, edge cases, and constraints before coding, then produces a feature plan artifact.

Core Features & Use Cases

  • Structured Socratic questioning to elicit requirements, edge cases, decisions, and constraints for a single feature or focused unit of work.
  • Produces a feature plan artifact that captures decisions, rationale, and any assumptions for downstream tasks.
  • Works from either a plan-project artifact or a standalone brief to align with broader system patterns.

Quick Start

Instruct the plan-feature skill with a brief feature brief or project context to begin the planning session and generate a feature plan artifact.

Frequently Asked Questions about plan-feature

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

FAQPage Schema
How do I plan software features to uncover edge cases before coding?

To plan software features and uncover edge cases before coding, you can use a Socratic questioning process that elicits requirements and constraints, ultimately producing a structured feature plan artifact capturing decisions and rationale.

What is a feature plan artifact and what should it include?

A feature plan artifact is a structured document capturing the scope, design decisions, rationale, and edge-case coverage for a focused unit of work. It ensures assumptions are documented for downstream task generation.

How do I start a feature planning session using a standalone brief?

To start a feature planning session using a standalone brief, provide the brief as context to begin a focused Socratic discussion that guides you through requirements gathering and produces a complete feature plan artifact.

Can I use an upstream project plan to guide feature planning?

Yes, you can use an upstream project plan to guide feature planning. The Socratic discussion works from either a project plan artifact or a standalone brief to align the feature with broader system patterns and constraints.

What is the best way to document design decisions and assumptions for downstream tasks?

The best way to document design decisions and assumptions for downstream tasks is to generate a feature plan artifact that explicitly captures your rationale, scope, and edge-case coverage during a structured planning discussion.