issue-planning

Create local draft issue files with acceptance criteria and implementation steps.

1|Updated Dec 8, 2023
One-click install
npx skills add https://github.com/hydrosolutions/SAPPHIRE_Forecast_Tools --skill issue-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-planning
Source: https://github.com/hydrosolutions/SAPPHIRE_Forecast_Tools/tree/main/.claude/skills/issue-planning
Command: npx skills add https://github.com/hydrosolutions/SAPPHIRE_Forecast_Tools --skill issue-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides structured problem analysis and implementation planning before coding, enabling teams to break work into well-defined issues.

Core Features & Use Cases

  • Structured planning workflow: from discovery to publication with clear ownership and criteria.
  • Draft-local workflow: creates LOCAL draft files that users review before GitHub publication.
  • Documentation focus: guides to fill problem statements, scopes, and acceptance criteria for issues.

Quick Start

Create a local draft issue file using the template and save it to doc/plans/issues.

Frequently Asked Questions about issue-planning

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

FAQPage Schema
How do I plan software development issues before starting to code?

To plan software development issues, use a structured workflow that creates local draft files from a template, documenting problem statements, scopes, and acceptance criteria before publication. This ensures implementation steps are well-defined.

What is the best way to write actionable GitHub issues for new features?

The best way to write actionable GitHub issues is to use a draft-local workflow that saves plans in a dedicated directory. This allows you to review structured problem analysis and acceptance criteria locally before publishing.

How does local draft issue tracking work for project management?

Local draft issue tracking works by creating draft files from a template and saving them in a local directory. You review these structured plans documenting scopes and implementation steps before moving them to GitHub.

Can I use a structured planning workflow for bug fixes and refactoring?

Yes, you can use a structured planning workflow for bug fixes and refactoring. It applies a repeatable process from discovery to publication, ensuring you document clear scopes, ownership, and acceptance criteria for these tasks.

Do I need GitHub to create structured software engineering plans?

No, you do not need GitHub immediately to create structured software engineering plans. The workflow creates local draft files saved in a local directory, which you review before final publication to GitHub.