plan-to-issues-csv
Skill2 starsChanged 5 months agoMITView on GitHub
Convert a `plan/*.md` execution plan into a uniquely named `issues/*.csv` snapshot for long-lived tracking. Use when the user explicitly mentions `$plan-to-issues-csv`, asks to turn a plan into issues CSV, says "plan 转 issues", "从 plan 生成 CSV", or wants to replace the deprecated `/prompts:plan_to_issues_csv` workflow. Read one plan file, derive 5-30 maintainable issues rows, and write `issues/YYYY-MM-DD_HH-mm-ss-<slug>.csv` in UTF-8 BOM.
In this repository12 other files it gives its agents.
- bug2csvSkill
- bugbatch-prepareSkill
- bugfix-comment-contextSkill
- bugfix-doneSkill
- bugfix-worktreeSkill
- debug-tag-addSkill
- debug-tag-clearSkill
- feature-doneSkill
- feature-prepareSkill
- feature-worktreeSkill
- plan-csv-executeSkill
- planSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill as the replacement for the deprecated custom prompt /prompts:plan_to_issues_csv.
- Very specific: line 22
If no path is provided, use the latest plan/*.md in the current workspace.
- Distinctive: line 23
Read the plan file first, then read only the minimum referenced files needed to fill gaps.
- Very specific: line 27
Always write a uniquely named snapshot under issues/.
- Very specific: line 28
Never create or update issues/issues.csv, issues.csv, or any other fixed summary CSV.
- Distinctive: line 29
Write the file as UTF-8 with BOM for Excel compatibility.
- Distinctive: line 30
Keep the CSV maintainable: default to one issue row per plan phase unless a phase clearly contains multiple independent workstreams.
- Distinctive: line 35
Use this exact header order:
- Distinctive: line 54
Ensure the CSV is parseable.
- Distinctive: line 55
Ensure every row has the full header width.
- Distinctive: line 56
Ensure all state columns only use the allowed enum values.
- Very specific: line 57
Ensure every row has a non-empty refs value.
- Distinctive: line 67
If file writes are blocked, return the full CSV in a code block and state the target path plus the UTF-8 BOM requirement.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plan To Issues CSV
Use this skill as the replacement for the deprecated custom prompt /prompts:plan_to_issues_csv.
Invocation
Preferred explicit trigger:
$plan-to-issues-csv plan/2026-03-31_10-00-00-login-flow.md
Natural-language triggers:
把这个 plan 转成 issues csv从 plan 生成可维护的 issues 快照
Input Rules
- Accept an optional plan file path.
- If no path is provided, use the latest
plan/*.mdin the current workspace. - Read the plan file first, then read only the minimum referenced files needed to fill gaps.
Output Rules
- Always write a uniquely named snapshot under
issues/. - Never create or update
issues/issues.csv,issues.csv, or any other fixed summary CSV. - Write the file as UTF-8 with BOM for Excel compatibility.
- Keep the CSV maintainable: default to one issue row per plan phase unless a phase clearly contains multiple independent workstreams.
- Target roughly 5-30 rows.
Fixed Header
Use this exact header order:
id,priority,phase,area,title,git_message,description,acceptance_criteria,test_mcp,review_initial_requirements,review_regression_requirements,dev_state,review_initial_state,review_regression_state,git_state,owner,refs,notesRow Defaults
dev_state:未开始review_initial_state:未开始review_regression_state:未开始git_state:未提交owner: emptynotes: emptyrefs: must not be empty; usepath:lineand separate multiple refs with;
Validation
Before finishing:
- Ensure the CSV is parseable.
- Ensure every row has the full header width.
- Ensure all state columns only use the allowed enum values.
- Ensure every row has a non-empty
refsvalue.
Reply Shape
Return only the essentials:
- Snapshot path
- Row count
- Any risks such as Excel/WPS file locks or limited source detail
- The next recommended command in skill form:
$plan-csv-execute <snapshot-path>
If file writes are blocked, return the full CSV in a code block and state the target path plus the UTF-8 BOM requirement.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

