workflow-plan

Generates implementation plans with acceptance matrices from GitHub issue research artifacts.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill workflow-plan-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-plan
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/opencode/skills/workflow/workflow-plan
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill workflow-plan-l0lxl0lw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a researched GitHub issue into a concrete, verifiable implementation plan is error-prone: plans often skip edge cases, lack testable acceptance criteria, or redo research that already exists. This Skill produces a structured plan with an explicit acceptance matrix before any code is edited. ## Core Features & Use Cases - Research Reuse: Loads prior research artifacts via handoff.py packets, spot-checks routes and persistence logic, and updates only invalidated findings instead of repeating broad research. - Acceptance Matrix: Defines input/scenario to observable response to state change to proving test, covering happy paths plus negative and edge cases such as malformed input, forbidden resources, and NULL/default rows. - Structured Plan Publication: Publishes a v2 Implementation plan JSON with contract revision, research fact IDs, steps, coverage map, and check manifest, then returns the plan URL and an /execute command. - Use Case: After researching a GitHub issue for a new API endpoint, run /plan to produce a 2-4 step implementation plan with targeted tests and a check manifest, ready for explicit /execute authorization. ## Quick Start Run /plan on the GitHub issue URL to generate an implementation plan with an acceptance matrix from the existing research artifact.

Frequently Asked Questions about workflow-plan

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

FAQPage Schema
How do I create an implementation plan from a GitHub issue?

Run /plan with the issue URL. The Skill loads the prior research artifact via handoff.py, spot-checks key findings, builds an acceptance matrix mapping scenarios to proving tests, and publishes a structured plan you authorize with /execute.

What is an acceptance matrix in implementation planning?

An acceptance matrix maps each input or scenario to its observable response, state change, and the test that proves it. It covers happy paths plus negative and edge cases like malformed input, forbidden resources, and NULL or default rows.

Does the planning step repeat research already done on an issue?

No. It reuses the existing research artifact and only updates findings invalidated by newer commits. Broad research or the specialist pipeline is not repeated; only named unresolved questions are delegated.

Can the plan modify the repository check manifest during planning?

No. Planning is read-only with respect to the repository manifest. It reads existing .opencode/workflow/checks.json definitions to select affected checks, and records justified baseline exclusions separately.

When should I request an independent plan audit?

Only for a named consequential uncertainty. The default flow performs one completeness self-check verifying every contract ID has a proving test or justified manual-review mapping, without adding another planning agent.