plan-from-issue
Skill0 starsChanged 6 months agoMITView on GitHub
Create a Plan Artifact before implementation begins.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/ai-coding-rules.mdcCursor rule
- .cursor/rules/architecture-rules.mdcCursor rule
- .cursor/rules/project-rules.mdcCursor rule
- implementation-reportSkill
- launch-checkSkill
- mvp-scope-checkSkill
- plan-from-issueSkill
- review-artifactSkill
- scale-automation-reviewSkill
- validate-ideaSkill
- implementation-reportSkill
- launch-checkSkill
- mvp-scope-checkSkill
- review-artifactSkill
- scale-automation-reviewSkill
- validate-ideaSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Read only the files above and the minimum relevant project files.
- Distinctive: line 52
Test plan is missing
≈ “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 From Issue
Purpose
Generate a Plan Artifact for Implementation Gate.
When to use
- A coding task is ready for planning
- Allowed files and tests need to be defined
- Implementation must not start yet
Read first
- AGENTS.md
- AI_WORKFLOW.md
- docs/11_stage_gates.md
- docs/13_human_gate_and_rollback.md
- .ai/artifacts/PLAN_ARTIFACT_TEMPLATE.md
Inputs
- Current issue or task
- Relevant files
- Relevant constraints
Outputs
- Plan Artifact
Steps
- Confirm the task is in Implementation Gate.
- Read only the files above and the minimum relevant project files.
- Define allowed files, forbidden files, test plan, and rollback plan.
- Fill the Plan Artifact.
- Require Human Owner approval before implementation and stop.
Human review
Human Owner must approve the plan, especially file scope, tests, and rollback plan.
Stop conditions
- Information is insufficient
- File boundary is unclear
- Test plan is missing
- Rollback plan is missing
- User has not approved the plan
- Any action would auto commit / push / merge / release
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.

