01-PLAN-spec

Name: 01-PLAN-spec
Availability: InStock
Author: Medtrics

Generate user-flow-centric feature specifications with markdown structuring and annotation conventions.

Updated Aug 23, 2026

Search Tags:#documentation #specification #requirements #product management #feature planning #user flow

Ready to run

npx skills add https://github.com/medtrics/medtrics-acumen --skill 01-plan-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: 01-PLAN-spec
Source: https://github.com/medtrics/medtrics-acumen/tree/main/templates/shared/skills/01-PLAN-spec
Command: npx skills add https://github.com/medtrics/medtrics-acumen --skill 01-plan-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams clearly define user journeys and write detailed specifications for new features, ensuring everyone understands what needs to be built and why.

Core Features & Use Cases

User Flow Definition: Maps out step-by-step user interactions.
Specification Writing: Generates comprehensive documentation for features.
Use Case: When planning a new user registration process, this Skill guides you to document each step a user takes, from entering their email to confirming their account, and outlines any broken or missing functionality in the current system.

Quick Start

Use the 01-PLAN-spec skill to write a new feature specification into the file named 'new-feature-spec.md'.

Frequently Asked Questions about 01-PLAN-spec

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

FAQPage Schema

How do I write a feature specification that maps out user flows for development teams?▼

To write a feature specification mapping user flows, document user journeys, current system states, and required changes using markdown structuring conventions. This ensures development teams understand step-by-step interactions, what needs building, and why.

What is user-flow-centric specification writing and when do I need it for product management?▼

User-flow-centric specification writing is documenting step-by-step user interactions and required system changes for new features. You need it during product planning to ensure teams understand user journeys, from entry to completion, and what functionality is currently missing.

How do I document current states and required changes when planning new feature requirements?▼

Document current states and required changes by generating detailed specifications that map user journeys and outline broken or missing functionality. This process decomposes work for development teams, ensuring clarity and testability through specific markdown annotation conventions.

Can I use markdown structuring to decompose product specs for new user registration processes?▼

Yes, you can use markdown structuring to decompose product specs for processes like user registration. It guides you to document each step a user takes, such as entering an email to confirming an account, while outlining missing functionality in the current system.

Does generating feature specifications require specific annotation conventions for testability?▼

Generating feature specifications requires adherence to specific markdown structuring and annotation conventions. This ensures the documented user journeys and required changes remain clear and testable for the development teams building the new features.

What is the best way to define user journeys and document missing functionality for feature planning?▼

The best way to define user journeys is generating detailed feature specifications that document step-by-step interactions and current system states. This outlines broken or missing functionality, ensuring development teams understand exactly what needs to be built.