agentleFS
Sign inStart free
roronoazoroshao369roronoazoroshao369/vibe-coding-os/skills/core/plan-from-spec/SKILL.md

plan-from-spec

Skill1 starsChanged 5 months agoMITView on GitHub

Translate an agreed specification into a concrete, verifiable implementation plan that captures technical context, sequencing, risks, and checks — without re-opening the behavioral "what". Use after a spec is agreed and before broad implementation, for any change that spans multiple files, introduces new dependencies, or carries meaningful risk. The agreed spec (goals, non-goals, acceptance criteria), repository conventions, known constraints, and the technical context deferred from the spec phase. A plan using templates/plan-template.md with technical context, ordered steps, spec traceability, risks,…

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use after a spec is agreed and before broad implementation, for any change that spans multiple files, introduces new dependencies, or …

    line 23
  2. Distinctive:

    Read the spec and confirm acceptance criteria are observable.

    line 33
  3. Distinctive:

    No traceability between steps and acceptance criteria.

    line 51
  4. Very specific:

    Not applied: upstream plan template text, command names, or CLI generation.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plan From Spec

Purpose

Translate an agreed specification into a concrete, verifiable implementation plan that captures technical context, sequencing, risks, and checks — without re-opening the behavioral "what".

When to use

Use after a spec is agreed and before broad implementation, for any change that spans multiple files, introduces new dependencies, or carries meaningful risk.

Inputs

The agreed spec (goals, non-goals, acceptance criteria), repository conventions, known constraints, and the technical context deferred from the spec phase.

Workflow

  1. Read the spec and confirm acceptance criteria are observable.
  2. Capture technical context separately: stack, data, interfaces, and constraints.
  3. Identify the smallest set of reviewable steps that satisfy the spec.
  4. For each step, name the files to touch and the expected outcome.
  5. Note risks, rollback points, and the verification command(s) per step.
  6. Trace each plan step back to one or more acceptance criteria.
  7. Hand the plan to task breakdown; do not start coding from the plan directly.

Outputs

A plan using templates/plan-template.md with technical context, ordered steps, spec traceability, risks, rollback, and verification.

Failure modes

  • The plan reopens behavioral decisions instead of implementing the spec.
  • Steps are too large to review or verify independently.
  • Technical context is missing, so tasks make hidden assumptions.
  • No traceability between steps and acceptance criteria.

Verification checklist

  • Every step maps to at least one acceptance criterion.
  • Technical context is explicit and separate from behavior.
  • Each step names files and expected outcome.
  • Risks, rollback, and verification are recorded.

Applied / Not Applied

  • Applied: the spec→plan transition and separated technical context from github/spec-kit.
  • Not applied: upstream plan template text, command names, or CLI generation. Reuses the existing local plan-template.md and plan-driven-execution skill.

Ghi chú tiếng Việt

Chuyển spec đã thống nhất thành kế hoạch triển khai cụ thể: tách technical context, chia bước nhỏ kiểm chứng được, truy vết từng bước về tiêu chí chấp nhận. Không mở lại quyết định hành vi. Dùng lại templates/plan-template.md. Liên kết: skills/core/plan-driven-execution/SKILL.md, skills/core/task-breakdown-from-plan/SKILL.md.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free