plan

Convert signed Agent Briefs into Lean PRDs and HITL/AFK GitHub Issues.

Updated Mar 2, 2022
One-click install
npx skills add https://github.com/ysuurme/azure_hello_world --skill plan-ysuurme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/ysuurme/azure_hello_world/tree/main/.agents/skills/plan
Command: npx skills add https://github.com/ysuurme/azure_hello_world --skill plan-ysuurme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It prevents unbounded work and re-proposing rejected ideas by converting an Agent Brief into a scoped Lean PRD and then decomposing it into trackable GitHub Issues with clear HITL/AFK labeling.

Core Features & Use Cases

  • Lean PRD synthesis: Produces a GitHub-issue formatted PRD with Problem Statement, User Stories, Tracer Bullet, Implementation Decisions, Testing Decisions, and Out of Scope.
  • Deduplication and de-risking: Searches existing open/closed GitHub issues and checks .out-of-scope.md to avoid rejected concepts and duplicates.
  • Vertical-slice issue decomposition: Breaks work into independently mergeable child issues where Issue #1 is the tracer bullet and each issue is labeled HITL or AFK.
  • Use Case: When a team has a new feature request, it quickly turns the idea into an actionable plan and CI-ready acceptance criteria before any code is written.

Quick Start

Use the plan skill to decompose a signed-off Agent Brief into a Lean PRD GitHub issue and create HITL/AFK child issues after checking for duplicates in existing GitHub issues and .out-of-scope.md.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I convert a feature brief into GitHub issues for development?▼

To convert a feature brief into GitHub issues, this Skill parses a signed Agent Brief into a Lean PRD and decomposes it into independently mergeable child issues labeled HITL or AFK using the gh CLI.

How do I prevent scope creep and re-proposed rejected concepts during feature planning?▼

Preventing scope creep during feature planning is achieved by searching existing GitHub issues and checking a `.out-of-scope.md` file to deduplicate work and block previously rejected concepts from being re-proposed.

What is a tracer bullet approach for decomposing a PRD into issues?▼

A tracer bullet approach for PRD decomposition designates Issue #1 as a vertical slice end-to-end proof of concept, followed by independently mergeable child issues that establish clear implementation and testing decisions.

Does this PRD generation tool require the gh CLI to create issues?▼

Yes, this PRD generation tool requires gh CLI access because it directly interacts with your repository to list existing open and closed issues for deduplication and to create new HITL/AFK child issues.

What sections should a Lean PRD include for GitHub issue decomposition?▼

A Lean PRD for GitHub issue decomposition should include Problem Statement, User Stories, Tracer Bullet, Implementation Decisions, Testing Decisions, and Out of Scope sections to ensure trackable development.

Can I label decomposed GitHub issues as Human-in-the-loop or Asynchronous?▼

You can label decomposed GitHub issues as HITL (Human-in-the-loop) or AFK (Away from keyboard) to clearly distinguish tasks requiring manual review from those that can be executed asynchronously.