ad-hoc-plan

Create a focused implementation plan for a single sprint task.

4|Updated Apr 15, 2026

Search Tags:#agile #task-management #sprint-planning #plan-writing #docs-plans #ad-hoc

Ready to run

npx skills add https://github.com/markhazlett/agent-harness --skill ad-hoc-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ad-hoc-plan
Source: https://github.com/markhazlett/agent-harness/tree/main/.claude/skills/ad-hoc-plan
Command: npx skills add https://github.com/markhazlett/agent-harness --skill ad-hoc-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool enables teams to quickly generate a concise, context-aware plan for a single task that fits into the current sprint, without the overhead of full goals analysis.

Core Features & Use Cases

Read existing sprint plans to understand context (what's done, what’s in progress, dependencies).
Enter Plan Mode to design implementation steps and capture them in a plan file.
Write the plan to docs/plans/YYYY-wNN/sprint-plans/ with a consistent PX.N-<type>-<slug>.md naming scheme.
Commit the plan on the active feature branch to keep history and traceability.
Use when you need a lightweight, time-boxed plan for small tasks or mid-sprint work.

Quick Start

Open the sprint docs, choose the next ad-hoc task, and create a new plan file that succinctly captures the goal and method.

Frequently Asked Questions about ad-hoc-plan

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

FAQPage Schema

How do I create a lightweight sprint plan for an ad-hoc task?▼

Sprint planning for ad-hoc tasks involves reading existing sprint plans for context, then writing a concise implementation plan file under docs/plans/YYYY-wNN/sprint-plans/. This approach captures goals and methods without the overhead of full goals analysis.

What is the best way to document implementation steps for mid-sprint work?▼

Documenting mid-sprint work is best handled by creating a focused, time-boxed plan file committed directly to the active feature branch. This maintains history and traceability while capturing done criteria without the overhead of full goals analysis.

Can I use existing sprint plans to provide context for new task plans?▼

Yes, the planning workflow reads existing sprint plans to understand current context, including what is done, what is in progress, and dependencies. This context-aware approach ensures new ad-hoc task plans align with ongoing sprint work.

How do I commit a task plan to a feature branch for traceability?▼

To commit a task plan for traceability, write the generated plan file to the docs/plans/YYYY-wNN/sprint-plans/ directory and commit it directly on the active feature branch. This keeps plan history linked to the code changes.

Does this ad-hoc planning approach require full sprint goals analysis?▼

No, ad-hoc planning specifically bypasses full sprint goals analysis to enable quick generation of concise, context-aware plans for single tasks. It is designed for lightweight, time-boxed planning for small tasks or mid-sprint work.