manage-issue-plan

Generate structured solution plans with file references and verification criteria for repository issues.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill manage-issue-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-issue-plan
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/manage-issue-plan
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill manage-issue-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague or high-level issue descriptions into concrete, codebase-aware solution plans that include exact file references, ordered steps, and verification criteria, then attaches the result to the repository's issues record to drive execution.

Core Features & Use Cases

  • Auto-detect analysis context: Includes prior analysis findings when present to ground the plan in known root cause and affected files.
  • CLI-driven planning: Builds a safe, parsed prompt and runs maestro delegate with gemini or qwen to generate a structured JSON solution.
  • Atomic attachment: Parses the solution, appends a history entry, and updates .workflow/issues/issues.jsonl without altering other issue fields.
  • Use Case: A developer needs an actionable patch plan for ISS-20260401-001 that lists file:line targets and verification steps to hand off to implementers or automated executors.

Quick Start

Run the manage-issue-plan skill with an issue ID to generate and attach a structured, file-referenced solution plan to .workflow/issues/issues.jsonl.

Frequently Asked Questions about manage-issue-plan

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

FAQPage Schema
How do I generate codebase-aware solution plans for repository issues?

To create verifiable solution plans, this skill builds a safe prompt and runs maestro delegate with gemini or qwen, producing ordered steps with file path references and verification criteria that attach to your issues.jsonl record.

What is the best way to convert high-level issue descriptions into actionable patch plans?

The best way to convert vague issues into patch plans is to include prior analysis findings for grounded planning, generating a structured JSON solution with ordered steps, estimated risk, and file:line targets for automated executors.

Does issue planning work with issues.jsonl records without altering other fields?

Yes, issue planning atomically updates issues.jsonl by appending a history entry and the solution plan to the matching issue record, ensuring other issue fields remain unaltered during the workflow.

Can I use prior analysis context to ground solution planning in known root causes?

Yes, you can include optional prior analysis context to ground solution planning, ensuring the generated steps and verification criteria accurately reflect the known root cause and affected files.

How to handle parse errors and prompt safety when generating structured JSON solutions?

To handle parse errors and prompt safety, the skill validates the generated structured JSON solution before atomically attaching it, preventing malformed outputs from corrupting your issues.jsonl records.