feature-plan

Generate feature plans with discovery narratives, user stories, and acceptance criteria.

1|Updated May 6, 2023

Search Tags:#collaboration #discovery #acceptance-criteria #design.md #feature-plan #repo-context #story.md

Ready to run

npx skills add https://github.com/TobiasLaross/dotfiles --skill feature-plan-tobiaslaross

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-plan
Source: https://github.com/TobiasLaross/dotfiles/tree/main/agentic/skills/feature-plan
Command: npx skills add https://github.com/TobiasLaross/dotfiles --skill feature-plan-tobiaslaross

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the end-to-end planning of new features by automatically generating a complete discovery narrative, acceptance criteria, and seed implementation notes that teams can act on.

Core Features & Use Cases

Structured discovery: Creates story.md and seed design.md, capturing decisions, constraints, and scope.
Decision-driven criteria: Produces testable acceptance criteria aligned with product goals and discovery outcomes.
Repo-context & seeds: Populates repository context and seeds design.md for implementation-era handoff, ready for review.

Quick Start

Generate a complete feature plan for a new idea, including story.md and seed design.md.

Frequently Asked Questions about feature-plan

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

FAQPage Schema

How do I generate user stories and acceptance criteria for new feature planning?▼

Feature planning generates a structured discovery narrative, testable acceptance criteria, and a user story by guiding teams through end-to-end validation. It captures product goals, decisions, and constraints directly into a story.md file for immediate team action.

What is the best way to document discovery outcomes and scope for a new product initiative?▼

Documenting discovery outcomes involves creating an annotated summary and seed design.md files that capture formal validation, traceable decisions, and scope constraints. This ensures implementation-era handoff records all product constraints and design seeds.

How do I create design seeds and repo-context for implementation handoff?▼

Creating design seeds and repo-context requires populating repository context and seeding design.md during the feature planning phase. This produces structured implementation notes and traceable decisions ready for developer review and downstream coding.

Can I use structured feature planning for internal initiatives, or is it only for new product ideas?▼

Structured feature planning applies to new product ideas, internal initiatives, and features requiring formal validation. It supports diverse contexts by generating discovery narratives and acceptance criteria aligned with specific product goals and scope.

Does end-to-end feature planning require any specific dependencies or tooling environments?▼

End-to-end feature planning requires no specific dependencies or tooling environments to generate the core story.md and design.md files. It provides optional tooling guidance and review steps to fit your existing collaboration workflow.