plan

Create actionable work plans with acceptance criteria and implementation steps.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/hotaq/Sprite_harmess --skill plan-hotaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/hotaq/Sprite_harmess/tree/main/.codex/skills/plan
Command: npx skills add https://github.com/hotaq/Sprite_harmess --skill plan-hotaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns broad, uncertain, or high-stakes requests into clear, actionable work plans so teams can start implementation with aligned scope, risks, and validation criteria.

Core Features & Use Cases

  • Adaptive planning flow: Detects whether a request needs user interviewing, direct planning, review of an existing plan, or consensus-driven deliberation.
  • Quality-gated output: Produces plans with acceptance criteria, implementation steps, risks, mitigations, verification, and traceable file references.
  • Consensus and review support: Runs planner, architect, and critic passes for high-stakes work and can refine plans through iterative review.
  • Execution handoff guidance: Captures ADRs, staffing guidance, and launch hints for downstream implementation workflows.

Quick Start

Ask the plan skill to create a work plan for your request and include any scope, constraints, or priorities you already know.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn vague software requirements into an actionable work plan?

To turn vague software requirements into a work plan, you can use an interview-driven scoping process that sequentially gathers details to produce a plan with clear implementation steps, risks, and mitigations.

What is the best way to create a software refactor plan with acceptance criteria and risk mitigations?

The best way to create a software refactor plan is to apply a quality-gated planning process that outputs implementation steps, risks, mitigations, and verification methods, ensuring your refactoring effort has evidence-backed validation.

How does consensus review work for high-stakes software engineering plans?

Consensus review for high-stakes software plans works by running sequential planner, architect, and critic passes to refine the plan through iterative review, ensuring scope, risks, and validation criteria are fully aligned before implementation.

Can I capture architecture decision records (ADRs) during the software planning workflow?

Yes, you can capture architecture decision records (ADRs) during the software planning workflow. The process includes execution handoff guidance that captures ADRs, staffing guidance, and launch hints to support downstream implementation tasks.

Does the planning workflow support reviewing and critiquing an existing software work plan?

Yes, the planning workflow supports reviewing and critiquing an existing software work plan. It evaluates the current plan against acceptance criteria and runs consensus-driven deliberation passes to refine scope, risks, and verification steps.