agentleFS
charliehzmcharliehzm/medharness/.claude/skills/openspec-continue-change/SKILL.md

openspec-continue-change

Skill85 starsChanged 6 months agoApache-2.0View on GitHub

Use this skill at Step 3 (after openspec-new-change) to expand proposal / design / specs into implementation-ready content. Iteratively fills out the technical approach, data model, contract specs, test strategy, and risk table. Stop when the change is "implementation-ready": every spec has acceptance criteria, design covers all PRD scope items, and the Compliance Design section is fully populated. Chinese trigger examples: "继续 OpenSpec", "OpenSpec 续写", "完善 design.md", "specs 填充". Do NOT use for task decomposition (next step), do NOT use to write code. Success = design.md covers 100% of in-scope PRD items, every spec has acceptance criteria, openspec validate passes.

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use openspec-ff-change, openspec-bulk-archive-change and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    openspec-ff-change

    Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

    Also in 61 projects that use this

  • MicrosoftSkill

    openspec-bulk-archive-change

    Archive multiple completed changes at once. Use when archiving several parallel changes.

    Also in 56 projects that use this

  • goernSkill

    draft-openspec-docs

    Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.

    Also in 3 projects that use this

  • goernSkill

    release-openspec

    Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is complete, what the next release step is, or to continue a release paused for human approval.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    openspec-update-change

    Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

    Also in 14 projects that use this

  • VercelSkill

    vercel-react-best-practices

    React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    Also in 3 projects that use this

  • +2 more from microsoft
  • +2 more from goern

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Distinctive:

    test hook (which test type, what data)

    line 49

“Common” is measured: kept by at least 6 in 10 of the 67 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

OpenSpec Continue Change

The "make it implementation-ready" expansion. After openspec-new-change scaffolds, this fills.

Quality bar — when to stop

The change is ready when every PRD in-scope item maps to ≥ 1 spec row, and every spec row has acceptance criteria.

Workflow

  1. PRD ↔ Spec mapping — list every in-scope item in PRD §3; ensure each has a spec id.
  2. Design body — technical approach for each spec, in design.md:
    • Data model (tables / messages / contracts)
    • API/IPC contracts
    • Component interaction diagram (mermaid acceptable)
    • Failure modes + recovery
    • Performance budgets
  3. Compliance Design — refine the section seeded in openspec-new-change:
    • Mark every L3/L4 field's flow path
    • Specify desensitization points
    • Specify audit log entries this change introduces
  4. Specs — for each spec row:
    • one-line behavior description
    • acceptance criteria (Given/When/Then or list)
    • test hook (which test type, what data)
  5. Risks — top 3 risks + mitigation (in design.md)
  6. Validate — run openspec validate (or openspec-ff-change for fast path) — must pass.

Common failure modes

  1. PRD item without spec — silent drop. Mitigation: explicit PRD↔Spec matrix at the top of design.md.
  2. Acceptance criteria as wishes — "the system should be fast". Mitigation: "P99 < 200ms on stage-mock data".
  3. Compliance afterthought — fill at the end. Mitigation: refine section every time you add a data-touching spec.
  4. Premature implementation — code samples in design.md > 30 lines. Mitigation: design says what, code says how (later).

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.