AGENT SKILL

to-spec

Use ONLY when the user explicitly requests this workflow in natural language or by name; a suggestion from another skill does not count. Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

License 许可
MIT
最近更新
2026-11-07
Stars
★ 4
Forks
1

01 前言 Front Matter

name
to-spec
slash
true
metadata
{ "opencode/autoinvoke": false }
description
Use ONLY when the user explicitly requests this workflow in natural language or by name; a suggestion from another skill does not count. Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

03 SKILL.md 正文

OpenCode Adapter

Workflow references in this text name Workshop Workflow Skills by their exact ID. Describe what you need in natural language; the skill descriptions decide when a skill fires, and an exact ID is never required to start a flow. User-only skills are exposed through the native skill menu; other skills can be discovered as needed. Load skills by exact ID with the native skill tool. Workshop does not register a custom command executor. Use only the current Workshop Primary Agent's native OpenCode capabilities and role boundaries. Never switch Primary Agents automatically.

This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.

The issue tracker and triage label vocabulary should have been provided to you — run setup-matt-pocock-skills skill if not.

Process

  1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.

  2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

Check with the user that these seams match their expectations.

  1. Write the spec using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label - no need for additional triage.

<spec-template>

Problem Statement

The problem that the user is facing, from the user's perspective.

Solution

The solution to the problem, from the user's perspective.

User Stories

A LONG, numbered list of user stories. Each user story should be in the format of:

  1. As an <actor>, I want a <feature>, so that <benefit>

<user-story-example>

  1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending </user-story-example>

This list of user stories should be extremely extensive and cover all aspects of the feature.

Implementation Decisions

A list of implementation decisions that were made. This can include:

  • The modules that will be built/modified
  • The interfaces of those modules that will be modified
  • Technical clarifications from the developer
  • Architectural decisions
  • Schema changes
  • API contracts
  • Specific interactions

Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.

Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.

Testing Decisions

A list of testing decisions that were made. Include:

  • A description of what makes a good test (only test external behavior, not implementation details)
  • Which modules will be tested
  • Prior art for the tests (i.e. similar types of tests in the codebase)

Out of Scope

A description of the things that are out of scope for this spec.

Further Notes

Any further notes about the feature.

</spec-template>

04 同仓库更多 Skills

MinZhi624
MinZhi624/opencode-personal-plugins

writing-for-agents

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

★ 4
MinZhi624
MinZhi624/opencode-personal-plugins

wizard

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

★ 4
MinZhi624
MinZhi624/opencode-personal-plugins

wayfinder

Use ONLY when the user explicitly requests this workflow in natural language or by name; a suggestion from another skill does not count. Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

★ 4
MinZhi624
MinZhi624/opencode-personal-plugins

wait-what

Use ONLY when the user explicitly requests this workflow in natural language or by name; a suggestion from another skill does not count. Stop. That last message did not land — re-pitch it.

★ 4
MinZhi624
MinZhi624/opencode-personal-plugins

triage

Use ONLY when the user explicitly requests this workflow in natural language or by name; a suggestion from another skill does not count. Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

★ 4
MinZhi624
MinZhi624/opencode-personal-plugins

to-tickets

Use ONLY when the user explicitly requests this workflow in natural language or by name; a suggestion from another skill does not count. Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

★ 4