skills.rest
CivicActions
CivicActionsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

issue-plan

Generates project-specific implementation plans with risks and milestones from tickets and codebase analysis.

2|Updated May 24, 2026
Search Tags:#workflow#planning#development#implementation#tickets#runbook
One-click install
npx skills add https://github.com/CivicActions/ai-runbook-jh --skill issue-plan-civicactions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-plan
Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/issue-plan
Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill issue-plan-civicactions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of ambiguous or poorly defined tickets by forcing a structured, step-by-step breakdown of work before any code is written, preventing scope creep and implementation drift.

Core Features & Use Cases

  • Structured Planning: Automatically generates an ordered, concrete task list, identifies risks, and defines acceptance criteria based on project-specific contracts.
  • Context Awareness: Integrates project-specific branch conventions, workflow states, and environment requirements to ensure plans are compliant with team standards.
  • Use Case: When a developer is assigned a complex feature request, they use this skill to generate a detailed plan file that maps out the implementation steps, identifies dependencies, and sets clear acceptance criteria before starting the build phase.

Quick Start

Use the issue-plan skill to generate an implementation plan for the ticket PROJ-1234.

Frequently Asked Questions about issue-plan

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

FAQPage Schema
How do I create an implementation plan for a development ticket?▼

Creating an implementation plan for a development ticket involves analyzing project-specific contracts and repository state to generate an ordered task list, identify dependencies, and define acceptance criteria before coding begins.

Why do I need a structured implementation plan before coding a feature?▼

You need a structured implementation plan before coding a feature to prevent scope creep and implementation drift by forcing a step-by-step breakdown of work, ensuring risks and dependencies are identified early.

Can I generate a technical roadmap that follows my team's branch conventions?▼

Yes, you can generate a technical roadmap that follows your team's branch conventions by integrating project-specific workflow states and environment requirements into the structured planning process.

What is the best way to identify risks and dependencies for a complex feature request?▼

The best way to identify risks and dependencies for a complex feature request is to analyze repository state and project contracts, mapping out implementation steps to set clear acceptance criteria.

Related Skills

Explore More Software Engineering Skills→
zerAdazerAda

gsd-research-phase

Research and validate a project phase implementation against the roadmap.

Community
Advanced
DFilipeSDFilipeS
22

px-implement

Execute implementation plans by writing code, running tests, and committing changes.

Community
Advanced
elijahmurrayelijahmurray
2

issue-start

Create a Git worktree and branch for a Linear ticket to start TDD.

Community
Intermediate
juvenaljuvenal
8

speckit-implement

Execute pre-planned feature implementation task lists in dependency-aware order with TDD.

Community
Advanced