公開プレイブック
次の仕事に使える進め方を見つけ、公開案件での実例を確かめられます。
garrytan/gstack · 2
Take a product opportunity from first principles through a scoped build, independent validation, launch, and learning.
Turn a consequential question into a decision and an executable plan. Start proportionally, investigate only what could change the choice, use specialist skills when the decision calls for them, then make one recommendation with a clear path to act. Use when: there is a real choice or problem to resolve, more than one viable move exists, or the result needs a deliberate plan. Do not use for: simple factual lookup, straightforward drafting, trivial reversible choices, or work where the requested action is already unambiguous. Working convention: keep intermediate work in runtime-private scratch state and return a concise decision brief and action plan in the conversation. Do not create tickets, files, Cases, or Records unless the requester explicitly asks for durable collaboration or an export.
obra/superpowers · 2
Turn a consequential question into a decision and an executable plan. Start proportionally, investigate only what could change the choice, use specialist skills when the decision calls for them, then make one recommendation with a clear path to act. Use when: there is a real choice or problem to resolve, more than one viable move exists, or the result needs a deliberate plan. Do not use for: simple factual lookup, straightforward drafting, trivial reversible choices, or work where the requested action is already unambiguous. Working convention: keep intermediate work in runtime-private scratch state and return a concise decision brief and action plan in the conversation. Do not create tickets, files, Cases, or Records unless the requester explicitly asks for durable collaboration or an export.
Turn a request into a well-designed, tested, reviewed, and verified software change.
epismoai/skills · 1
Use when someone has an Epismo account but no Playbook yet, and does not know what to write. Sets up the surface and the Epismo skill, finds the recurring work already living in their environment, filters it to the one thing a single skill cannot carry, writes it with input, output, and harness pinned so a stranger's agent can rerun it, then rehearses it against real past evidence and publishes it on the owner's go-ahead. Ends in one session with a working setup and one published, aliased Playbook — not a library plan. Quickstart — choose an install route, then say one sentence. macOS or Linux: `curl -fsSL https://epismo.ai/install.sh | sh`. Windows PowerShell: `irm https://epismo.ai/install.ps1 | iex`. npm: `npm install -g epismo`. You can also download native binaries and SHA-256 checksums directly from https://github.com/epismoai/cli/releases. Then run `epismo login`. MCP: add https://mcp.epismo.ai/ as a Streamable HTTP server with OAuth. Then prompt your agent: "Use pb:epismo/first-playbook to build my first Playbook." It will read this guidance, look at what you already do, and come back with a candidate — you only decide what to publish and to whom. Everything else is in the Steps below. Execution convention: keep intermediate materials in runtime-private scratch state, not in the user’s repository. After each meaningful step, present a concise, human-readable summary in the conversation. Create a local file only when the user explicitly asks to export one.
mattpocock/skills · 1
Turn a consequential question into a decision and an executable plan. Start proportionally, investigate only what could change the choice, use specialist skills when the decision calls for them, then make one recommendation with a clear path to act. Use when: there is a real choice or problem to resolve, more than one viable move exists, or the result needs a deliberate plan. Do not use for: simple factual lookup, straightforward drafting, trivial reversible choices, or work where the requested action is already unambiguous. Working convention: keep intermediate work in runtime-private scratch state and return a concise decision brief and action plan in the conversation. Do not create tickets, files, Cases, or Records unless the requester explicitly asks for durable collaboration or an export.
phuryn/pm-skills · 1
Move from a customer problem through discovery, validation, strategy, a build-ready PRD, launch, measurement, and the next product decision.