Skip to content
AI & Agents
Skill

/to-prompt

Create a handoff brief for another LLM to implement. Preserve accepted decisions and write to docs/prompts/; excludes one-shot questions and end-user copy.

BOOST
From plugin
pedronauck-skills
63787 skills1 command
Install
$ npx -y skills add pedronauck/skills --skill to-prompt --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/to-prompt

Context preview

The summary Claude sees to decide when to auto-load this skill.

Create a handoff brief for another LLM to implement. Preserve accepted decisions and write to docs/prompts/; excludes one-shot questions and end-user copy.

SKILL.md

to-prompt.SKILL.md
name: to-prompt
description: "Create a handoff brief for another LLM to implement. Preserve accepted decisions and write to docs/prompts/; excludes one-shot questions and end-user copy."
disable-model-invocation: true
metadata:
  author: Pedro Nauck
  github: https://github.com/pedronauck
  repository: https://github.com/pedronauck/skills

To Prompt

Write a **brief**, not a solution. The brief carries everything the receiving LLM needs to choose the implementation itself — the problem, the current state, the requirements, the constraints — and preserves any implementation constraints or approved plan already supplied by the user. Leave undecided design choices to the receiver; do not erase accepted decisions to manufacture an open-ended problem.

Every brief is a file: `docs/prompts/<YYYYMMDD-HHmm>_<slug>.md` (e.g. `docs/prompts/20260709-1745_fix-auth-redirect.md`).

Steps

1. **Classify the task** — bug fix, improvement, or feature — and draft a one-paragraph statement of the problem and the outcome wanted. 2. **Gather the evidence.** Read the code paths involved; quote current code as it exists; capture the relevant error/log excerpts, excluding credentials and unrelated private data; note environment and recent changes. *Done when:* every claim in the brief is backed by something you actually read or ran. 3. **Write the brief from the template.** Copy `assets/brief-template.md` to `docs/prompts/<YYYYMMDD-HHmm>_<slug>.md` (create the directory if absent; slug = lowercase-hyphenated summary; timestamp = now). Fill the applicable sections and remove guidance comments. Record consequential unknowns; omit irrelevant sections. 4. **Check decision fidelity.** Separate user-approved constraints from suggestions and unresolved choices. Preserve the requested outcome and authorization; avoid introducing new implementation mandates. 5. **Hand off.** Reply with the file path and a one-line summary of what the brief asks for.

Bundled files

  • `assets/brief-template.md` — the brief's skeleton and per-type coverage guidance; the single source of truth for what a complete brief contains.
Read more
Ships withpedronauck-skills

A curated collection of 87 agent skills for Claude Code and compatible AI coding assistants — 40 original (⭐️), 34 hand-picked (💎), and 13 marketing & business (📣).

Get the whole plugin
Stats
637
Stars
89
Forks
Maintained
Maintenance
Python
Language
1mo ago
Last commit
7mo ago
Created
4h ago
Added

Repo: pedronauck/skills

Other skills on pedronauck-skills.