Requirements Planning

product-lens is a decision-support skill for validating the why before building, pressure-testing product direction, and turning vague requests into sharper briefs. Use product-lens when you need a quick product diagnosis, not a full spec, and want a clearer go/no-go answer before engineering planning.

product-capability turns PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan with constraints, invariants, interfaces, and unresolved decisions. Use it for Requirements Planning when multi-service work needs a durable product-capability skill artifact instead of vague planning prose.

inventory-demand-planning is a retail decision-support skill for forecasting demand, setting safety stock, planning replenishment, and estimating promotional lift across stores and DCs. Use it to guide inventory-demand-planning usage with structured inputs, practical constraints, and clearer planning tradeoffs.

brainstorming is a pre-implementation skill that explores context, asks clarifying questions one at a time, and requires design approval before any code. Includes an optional visual companion and strong support for Requirements Planning.

writing-plans helps turn a spec or requirements doc into a detailed implementation plan with file-level guidance, task sequencing, testing steps, and a review prompt before coding starts.

project-planner is an AI skill for turning project ideas into executable plans with deliverables, task breakdowns, dependencies, milestones, estimates, and risk-aware sequencing. It is self-contained in SKILL.md and best for scoping work, building WBS-style plans, mapping critical paths, and creating first-pass delivery plans from clear goals and constraints.

team-composition-analysis helps founders, operators, and recruiting leads plan early-stage startup hiring by stage, ARR, and budget. Use it to sequence roles, shape team structure, and estimate compensation and equity from pre-seed through Series A.

security-requirement-extraction turns threat models and business context into testable security requirements, user stories, acceptance criteria, and backlog-ready outputs for Requirements Planning.

The track-management skill helps teams create, manage, and complete Conductor tracks with spec.md, plan.md, lifecycle metadata, and tracks.md workflow guidance.

task-coordination-strategies helps teams decompose complex work, map dependencies, define acceptance criteria, and coordinate parallel agent or contributor workflows with clearer ownership and fewer merge conflicts.

ralph-plan is a planning skill that turns rough engineering requests into structured ralph-loop commands with context, setup, tasks, testing, and iterative clarification.

The planning-and-task-breakdown skill turns a spec, feature request, or messy goal into ordered, implementable tasks with clear dependencies and acceptance criteria. It helps with planning-and-task-breakdown for Project Management, parallel work, and scope estimation while reducing guesswork before implementation.

idea-refine is a structured ideation skill that turns rough concepts into clearer, buildable directions through divergent thinking, critique, and convergence. It helps founders, product leads, engineers, and AI agents with Requirements Planning by producing a concrete one-pager with assumptions, scope, and a not-doing list.

grill-me turns an AI assistant into a structured reviewer for plans and designs, asking one question at a time, resolving decision branches, and using the codebase when possible to stress-test requirements.

write-a-prd helps turn a vague feature idea into a GitHub-issue-ready PRD through repo exploration, relentless user interviews, and module design. Best for Requirements Planning in an existing codebase.

ubiquitous-language turns domain conversations into a DDD-style glossary, flags ambiguity and synonyms, proposes canonical terms, and writes `UBIQUITOUS_LANGUAGE.md`. Useful for terminology alignment across docs, APIs, product language, and ubiquitous-language for Technical Writing.

prd-to-plan turns a PRD into a phased implementation plan using tracer-bullet vertical slices. It guides repo exploration, captures durable architecture decisions, and saves the final Markdown plan in ./plans/ for Requirements Planning.

The opportunity-solution-tree skill helps Product Management teams build an Opportunity Solution Tree for product discovery: map a desired outcome to opportunities, solutions, and experiments. Use it to structure discovery work, compare options, and decide what to build next with less solution bias.

identify-assumptions-new helps Product Management teams stress-test a new product idea by surfacing risky assumptions across 8 categories, including Value, Usability, Viability, Feasibility, Ethics, Go-to-Market, Strategy & Objectives, and Team. Use it to map startup risks, clarify what must be true, and turn discovery gaps into tests.

identify-assumptions-existing helps you stress-test a feature idea in an existing product by surfacing risky assumptions across Value, Usability, Viability, and Feasibility. It uses PM, designer, and engineer perspectives plus a devil’s advocate lens for Strategic Planning and pre-build risk review.

Analyze and prioritize feature requests by theme, strategic fit, impact, effort, and risk with the analyze-feature-requests skill. Use it to review customer feedback, triage a backlog, and make defensible product decisions, including analyze-feature-requests for Competitive Analysis when comparing demand across competitors.

wwas is a prompt skill for Requirements Planning that turns rough ideas into Why-What-Acceptance backlog items. Use the wwas skill to capture business context, define the change clearly, and write testable acceptance criteria for sprint-ready work.

Use the user-stories skill to turn features into backlog-ready stories with the 3 C's, INVEST criteria, design links, and testable acceptance criteria. Ideal for writing user stories, splitting features into backlog items, and user-stories for Requirements Planning with clearer scope and less guesswork.

Use sprint-plan to turn a backlog into a realistic sprint plan with capacity estimation, story selection, dependency mapping, and risk review. It is ideal for Project Management when you need a sprint-plan guide that helps filter unready work, balance scope against velocity, and prepare for sprint planning with less guesswork.