plan-task

Convert user requests into phase-driven planning pipelines with Work-system integration.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/This-HW/hantu_quant --skill plan-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-task
Source: https://github.com/This-HW/hantu_quant/tree/main/.claude/skills/plan-task
Command: npx skills add https://github.com/This-HW/hantu_quant --skill plan-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

plan-task provides a structured, phased approach to turning vague requests into concrete, executable planning artifacts, including automatic Work-system integration.

Core Features & Use Cases

  • Phase-based planning pipeline (Phase 0–5) with scalable paths for Small/Medium/Large projects.
  • Automatic Work-system integration: folder creation, frontmatter, progress tracking, and decisions logging.
  • Optional multi-perspective reviews for Medium/Large scopes to validate planning results.

Quick Start

Provide a clear project request to plan-task and it will generate a Work-ready plan and trigger Phase 0.

Frequently Asked Questions about plan-task

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

FAQPage Schema
How do I convert vague project requirements into a phase-based implementation plan?

Structured planning analyzes your request and converts it into a phase-driven pipeline, prompting clarifying questions to resolve P0 ambiguities and producing a concrete, executable implementation plan with traceable decisions.

What is the best way to automate project setup and documentation for new requests?

Automating project setup uses a Work-system integration that triggers folder creation, generates frontmatter, logs decisions, and tracks progress automatically as your formal planning pipeline progresses through its phases.

Can I use phase-based planning for both small tasks and large scale projects?

Phase-based planning supports scalable scope paths categorized as Small, Medium, or Large, automatically adjusting the pipeline depth and offering optional multi-perspective reviews to validate planning results for Medium and Large projects.

How do I start the planning pipeline once I have a project request?

To start the planning pipeline, provide a clear project request and the system will generate a Work-ready plan, automatically trigger Phase 0, and initiate the formal planning and documentation setup process.

Why does my planning pipeline prompt me with clarifying questions before generating documentation?

Clarifying questions are prompted during planning to resolve critical P0 ambiguities in your request, ensuring the generated implementation plan remains concrete, accurate, and fully traceable before proceeding further.

What are the limitations of automated work-system planning for requirement documentation?

Automated work-system planning requires a clear initial request to function effectively, and multi-perspective reviews to validate results are only available for Medium and Large project scopes, leaving Small scopes without this validation.