agentsclimarketplace
Sign in

To specs

Skill uluserdar/claude-ecosystem/skills/to-specs

Turns the current conversation (and, if relevant, an existing release-plan step) into a full spec/PRD — no interview, just synthesis of what's already been discussed — and offers to publish it as a GitHub issue. ALWAYS trigger on explicit phrases like "turn this into a spec", "write a spec for this", "spec this out", "convert this step into a spec", "make this a PRD", "spec out what we just discussed". Do NOT trigger for creating a brand-new release plan from scratch (that's create-plan), for marking an existing step's progress status (Done/In Progress/etc.), or when the user just wants a quick summary rather than a structured spec document.From its SKILL.md

Install
npx -y skills add uluserdar/claude-ecosystem --skill to-specs

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

  • 1 stars1 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

2.4 KB, as published. Nobody here has run it

to-specs

This skill's only job is to hand off to the spec-writer subagent, which synthesizes a spec from the current conversation and codebase context and writes it to disk. Do not draft the spec yourself, do not interview the user for spec content, and do not write any files yourself.

Instructions

  1. Invoke the spec-writer subagent via the Agent tool, passing along:
    • Everything relevant that's been discussed in this conversation so far (the spec is synthesized from this — never re-ask the user to restate it).
    • Any explicit reference the user made to a release-plan plan/phase/step this spec is for, if mentioned.
    • Model: read agentModel["spec-writer"] from .claude/claude-ecosystem-settings.json, falling back to agentModel.default; pass whichever resolves as the model parameter, or omit model entirely if neither is set.
  2. spec-writer owns target-file detection, codebase exploration, seam sketching, spec synthesis, file writing, and the optional GitHub-publish step end to end — do not duplicate or second-guess its work.
  3. Once spec-writer finishes, relay its summary (file path, and issue URL if one was created) back to the user.
<constraints> - This skill delegates 100% of spec synthesis and generation work to `spec-writer`. It has no standalone spec-writing logic of its own beyond routing. - This skill runs standalone only — it is never invoked by, and never invokes, `create-plan` or `plan-writer`. Creating a new release plan is entirely out of scope here. - This skill does not interview the user for spec content — it only synthesizes from what's already in the conversation. </constraints> </content>

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.