SubmitLog in
c/productivity › command
0votes

Conversation to spec (Matt Pocock)

Skill
submitted by u/client to c/productivity · 0 uses

Turns what you've discussed into a structured spec and files it in your issue tracker.

Takes the current conversation and writes it up as a spec with problem statement, solution, user stories, implementation and testing decisions, and scope, then publishes it to the project's issue tracker. It doesn't interview you again; it just synthesizes. Manual use only (run /to-spec), and it needs access to your tracker, for example via the gh CLI.

Try asking:

  • "/to-spec"
  • "/to-spec and file it as a GitHub issue"
  • "/to-spec for the export feature we just discussed"

Source: mattpocock/skills · MIT · by Matt Pocock

0 commentsreport

Install this skill

Skills are folders with a SKILL.md file. Claude loads one on its own when a task matches its description. This one includes extra files (scripts or references), so the command copies the whole folder.

Claude Code plugin (easiest, stays up to date)
/plugin marketplace add mattpocock/skills
/plugin install mattpocock-skills@mattpocock
Claude Code: for every project
npx degit mattpocock/skills/skills/engineering/to-spec ~/.claude/skills/to-spec
Claude Code: this project only (commit it to share with your team)
npx degit mattpocock/skills/skills/engineering/to-spec .claude/skills/to-spec
View SKILL.mdSource

Made by Matt Pocock, MIT license. Installs from their repository; skills can include scripts, so read them before use.

In the Claude apps, zip the folder and upload it under Settings → Capabilities → Skills.

More from c/productivity

See all of c/productivity →
0 comments

Log in to join the discussion.