Capture and persist pre-plan discussions into structured deep-plan artifacts.
npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill plan-deep
Please help me install this Agent Skill. Skill: plan-deep Source: https://github.com/HypoxanthineOvO/Hypo-Workflow/tree/main/skills/plan-deep Command: npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill plan-deep
Deep Plan provides a durable pre-plan discussion lifecycle to capture requirements, architecture reasoning, decisions, and readiness blockers before ordinary Hypo-Workflow planning.
Create a new deep plan package and begin the first-principles questioning to start the drafting lifecycle.
High-intent search queries and answers about installing and using this skill.
A deep plan captures pre-plan discussions for long-horizon planning by persisting requirements, architecture reasoning, and readiness blockers into structured artifacts before regular workflow planning begins.
The best way to document requirements for long-horizon planning is applying a multi-stage lifecycle that moves through drafting, researching, architecture mapping, and readiness validation to produce structured artifacts.
You convert pre-plan discussions into standard plan inputs by passing readiness validation, which transitions the deep-plan package into a converted state and produces a compact plan input for regular planning.
Yes, the pre-plan discussion lifecycle explicitly supports readiness blockers, applying readiness validation during the lifecycle stage before allowing conversion into standard plan inputs.
A limitation of using a deep plan for workflow pre-planning is that it requires moving through multiple lifecycle stages including drafting, architecture mapping, and readiness validation before conversion into standard inputs is possible.
davidabeyerExtract user-selected proposals into a structured brief for the /plan command.
skyoxuEdit BMAD-standard PRDs through discovery, review, and validation workflows.
cuiossMerge derived module data with LLM-enriched annotations to map project architecture.
tkstangReview unstaged, staged, file lists, or commit ranges in Git changes.
