Plan from rfc

Skill IcodeNet/agent-skills/skills/plan-from-rfc

Generate a phased implementation plan from an RFC, design doc, or spec (URL or file). Use when the user provides an RFC/design document and wants an implementation plan, migration plan, or execution-ready PR breakdown from it.From its SKILL.md

Install

npx -y skills add IcodeNet/agent-skills --skill plan-from-rfc

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 382 tokens by cl100k_base, as published. Nobody here has run it

Plan From RFC

Turn an RFC or design document into a phased, executable delivery plan.

Input collection

If any input is missing, ask the user first:

RFC source (URL or workspace file path)
Goal (implement, refactor, migrate, or review)
Constraints (timeline, risk tolerance, no-behavior-change, testing scope)
Output depth (high-level or execution-ready PR breakdown)

If the RFC source cannot be accessed, ask the user to paste key sections (goal, scope, constraints, decisions, risks), then continue with explicit assumptions.

Analysis steps

Extract: problem statement, goals and non-goals, constraints, accepted decisions, dependencies.
Identify ambiguities and missing information.
Convert into a phased delivery plan with small, low-risk increments.
Keep behavior-preserving constraints explicit when requested.

Output format (exact order)

Context Summary
Assumptions
Scope In / Scope Out
Implementation Plan — phased steps, per-step dependencies, rollback notes
PR Breakdown — one bullet per PR with intent, likely files/areas touched, and risk
Test Strategy — targeted tests first; broader checks only where risk justifies
Risks and Mitigations
Open Questions for Approval

Rules

Prefer small PRs over broad multi-domain PRs.
Highlight hotspot/conflict-prone files when likely.
Do not invent undocumented architecture decisions; mark them as open questions.
If the user asked for a plan only, do not implement code.
Keep commands aligned with the repo's package scripts when possible.
To stress-test the resulting plan, follow with the plan-critic skill.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.