Create Specification Issues
Planning work from a long conversation can lose decisions, constraints, and testing intent. This skill turns existing context into a structured spec and publishes it to the issue tracker.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "to-spec" from https://skillstore.io/skills/mattpocock-to-spec.md and its manifest at https://skillstore.io/api/skills/mattpocock-to-spec/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "to-spec". A conversation about adding account balance notifications.
Expected outcome:
A tracker issue with a problem statement, solution, user stories, implementation decisions, testing decisions, scope limits, and notes.
Using "to-spec". A bug fix discussion with agreed validation behavior.
Expected outcome:
A structured spec that captures expected behavior, affected modules, test coverage, and ready-for-agent labeling.
Using "to-spec". A planning thread for a cross-team API change.
Expected outcome:
A product specification that records API decisions, user impact, ownership notes, testing plans, and out-of-scope work.
Both static findings are false positives caused by markdown inline backticks around a setup slash command and a label name in SKILL.md. The skill is prompt-only, with no scripts, network calls, or executable code. No prompt injection or data exfiltration intent was found.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/mattpocock-to-spec/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/mattpocock-to-spec?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/mattpocock-to-spec?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/mattpocock-to-spec/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/mattpocock-to-spec.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>mattpocock. (2026). to-spec security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/mattpocock-to-spec/audits/2@techreport{mattpocock-mattpocock-to-spec-2026,
author = {mattpocock},
title = {to-spec security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/mattpocock-to-spec/audits/2},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "to-spec security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
- name: "mattpocock"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/mattpocock-to-spec/audits/2"
identifiers:
- type: other
value: "skillstore:mattpocock-to-spec:audit:2"
description: "Skillstore immutable audit report identifier"
Convert a design discussion into a complete feature specification before implementation starts.
Capture decisions and testing expectations so another agent or developer can build from a tracker issue.
Turn scattered conversation context into structured issues with scope, user stories, and follow-up notes.
Use to-spec to turn this conversation into a specification issue for the feature we discussed.
Use to-spec to write a tracker-ready spec for this bug fix, including expected behavior, decisions, tests, and out-of-scope items.
Use to-spec to publish a spec that another coding agent can implement. Preserve our implementation decisions and testing approach.
Use to-spec after reviewing the repository context and conversation. Include affected modules, API decisions, data changes, testing decisions, and ownership notes.
Author
mattpocockLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
1bf22d3f5624f0760cf4b4337c7dfa2efb3bd403
Maintenance freshness
7/18/2026
Usage
1 downloads · 0 views
File structure
📄 SKILL.md
Guide TDD with Red-Green-Refactor
Test-first work often becomes brittle when teams test internals or write too many tests upfront. This skill guides Codex, Claude, and Claude Code through behavior-focused red-green-refactor cycles.
Sharpen Plans and Create Decision Documentation
Unresolved assumptions weaken plans and technical designs. This skill conducts a focused interview and uses domain modeling to produce ADRs and a glossary.
Stress-Test Your Plan Before Building
Unresolved decisions can make a plan expensive to change during implementation. This skill interviews you systematically and recommends an answer for each decision.
Create Agent Skills
Teams need consistent skill files that agents can discover and use correctly. This skill guides authors through structure, descriptions, examples, scripts, and review checks.
Build Focused Logic and UI Prototypes
Design decisions are difficult to evaluate before users can interact with them. This skill builds disposable prototypes that expose state behavior or compare interface variants.
Pressure-test plans with grilling interviews
Plans and designs often fail because weak assumptions are found too late. This skill starts a focused grilling session that challenges gaps before execution begins.
Create Confirmation-Driven PRDs
by yunshu0909
PRD work often becomes vague, unconfirmed, or hard to hand off. This skill guides structured discovery, story confirmation, diagrams, and final PRD generation.
Create Ralph TUI PRDs
by subsy
Teams need clear requirements before assigning work to AI coding agents. This skill turns feature ideas into structured PRDs with user stories and quality gates for ralph-tui workflows.
Plan Software Projects With Structured Documents
by Dwsy
Software projects often fail when requirements, design choices, and tasks are unclear. This skill turns project ideas into structured planning documents for Claude, Codex, and Claude Code workflows.
Create IEEE 830 SRS Documentation
by DoubleslashSE
Requirements teams need consistent SRS documents that are complete, traceable, and testable. This skill provides an IEEE 830 structure, templates, and validation checklists.
Plan Requirements with Interactive Questions
by DNYoussef
Ambiguous project requests often lead to missing requirements and rework. This skill guides Claude, Codex, and Claude Code through structured question batches.
Plan Complex Coding Changes
by tencentcloudbase
Large coding changes often fail when scope, design, and acceptance criteria are vague. This skill guides Claude, Codex, and Claude Code through requirements, design, tasks, and staged confirmation.