Verified:GitHub

planner

Turn vague ideas into structured specifications with milestones and acceptance criteria.

Updated Dec 6, 2025

Search Tags:#planning #specification #clarification #milestones #task-management #product-management #acceptance-criteria

Ready to run

npx skills add https://github.com/arttttt/CMIDCABot --skill planner-arttttt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/arttttt/CMIDCABot/tree/main/.gemini/skills/planner
Command: npx skills add https://github.com/arttttt/CMIDCABot --skill planner-arttttt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn vague ideas into clear, actionable specifications and task plans by guiding structured planning conversations.

Core Features & Use Cases

Guided spec creation: Convert requirements into precise, testable acceptance criteria and milestones.
Proactive clarification: Identify gaps early by asking targeted questions before work begins.
Use Case: When starting a new feature, use Planner to draft a complete spec and PR-ready task list.

Quick Start

Provide an initial product idea or problem statement to Planner and request a structured specification outline.

Frequently Asked Questions about planner

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

FAQPage Schema

How do I turn a vague product idea into a structured specification?▼

To turn a vague idea into a structured specification, provide your initial product problem statement to prompt a guided planning conversation that identifies gaps and clarifies scope boundaries. This process delivers a ready-to-use specification outline with clear milestones.

What is the best way to define acceptance criteria for a new feature?▼

The best way to define acceptance criteria is through guided spec creation that converts your requirements into precise, testable conditions. This ensures all criteria are directly linked to the defined scope boundaries and project milestones.

How do I identify scope gaps before starting product development?▼

You identify scope gaps before product development by using proactive clarification, which asks targeted questions about your initial idea before work begins. This surfaces ambiguity early and prevents undocumented requirements from slipping into development.

Can I generate a PR-ready task list from a brief problem statement?▼

Yes, you can generate a PR-ready task list from a brief problem statement by applying a structured planning workflow. It transforms basic input into actionable milestones and testable acceptance criteria suitable for immediate development.

Does this planning approach work for documenting existing feature workflows?▼

Yes, this planning approach works for documenting existing feature workflows by applying structured specification techniques to your current processes. It resolves ambiguity and outputs clear documentation boundaries for product management tasks.