skills.rest
minfengyuan
minfengyuanCOMMUNITY
Explore all skills by this author →
GitHub

autoplan

Convert vague user requests into executable implementation plans with objectives and verification strategies.

1|Updated Mar 27, 2026
Search Tags:#planning#scoping#implementation#discovery#engineering-review#product-review
One-click install
npx skills add https://github.com/minfengyuan/harness-knowledge-base --skill autoplan-minfengyuan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/minfengyuan/harness-knowledge-base/tree/main/skills/autoplan
Command: npx skills add https://github.com/minfengyuan/harness-knowledge-base --skill autoplan-minfengyuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts broad or underspecified user requests into narrow, testable, and execution-ready implementation plans so teams avoid premature coding and hidden assumptions.

Core Features & Use Cases

  • Clarification & discovery: extracts goals, audiences, constraints, and implied scope and runs office-hours style discovery when needed.
  • Plan drafting: produces objectives, major workstreams, interfaces or behavior changes, and a verification strategy.
  • Review orchestration: conditionally applies product-level and engineering-level review passes and merges feedback into a final plan suitable for implementation.

Quick Start

Use autoplan on a vague feature request to produce an execution-ready implementation plan with objectives, major workstreams, and verification steps.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I turn a vague feature request into an executable implementation plan?▼

Implementation planning converts vague requests by extracting goals, audiences, and constraints, then drafting step-by-step objectives, major workstreams, interfaces, and verification strategies into an execution-ready plan.

What is the best way to scope large tasks and extract hidden assumptions during product discovery?▼

Scoping large tasks requires running discovery sessions to extract implied scope and constraints, ensuring hidden assumptions surface before drafting objectives, workstreams, and behavior changes for execution.

How do I decide whether to run a product review or engineering review pass on a drafted plan?▼

Review orchestration conditionally applies product-level and engineering-level review passes to a drafted plan, evaluating interfaces and behavior changes before merging feedback into the final implementation plan.

Does implementation planning work for underspecified user requests with no clear verification strategy?▼

Implementation planning handles underspecified requests by running office-hours style discovery to clarify goals, then producing a verification strategy alongside objectives and workstreams to ensure testable execution.

What should be included in an executable implementation plan to avoid premature coding?▼

An executable implementation plan should include step-by-step objectives, major workstreams, interfaces or behavior changes, verification strategies, and documented assumptions to prevent premature coding and hidden scope creep.

Related Skills

Explore More Product & Management Skills→
OzeroHAXOzeroHAX
32

planning-requirements-extraction

Extract verifiable requirements and acceptance criteria from user requests.

Community
Basic
ddobrinddobrin
39

plan-executor

Execute architectural plans into atomic, testable code changes with verification.

Community
Advanced
Jicate-SolutionsJicate-Solutions

executing-plans

Execute implementation plan tasks in batches with review checkpoints.

Official
Intermediate
LucaDeLeoLucaDeLeo
1

bmad-bmm-create-epics-and-stories

Decompose natural-language project goals into epics and user stories with acceptance criteria.

Community
Intermediate