Menu
Use when finishing a piece of work - the closing pass that prevents a "done" piece from coming back at you a week later
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"
Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.
Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.
| name | wrapping-up-a-piece |
| description | Use when finishing a piece of work - the closing pass that prevents a "done" piece from coming back at you a week later |
| kind | workflow |
| audience | knowledge-worker |
| ai-tools | any |
| complexity | simple |
| time | 5-15 min |
| version | 1.0.0 |
| source | bundled |
Runs a structured closing pass on a piece of work: handoff, archive, follow-up. Distinct from verifying-before-shipping (which is "is this done?"). This is "now that it's done, what closes it for good?"
A clean closure: handoff message sent, artifacts archived, deferrals captured, retrospective if warranted.
This is a workflow.
Identify who needs the work next (or who needs to know it's done). Send them: a one-line summary, a link to the artifact, a one-line "what they should know" note.
Put the artifact where future-you (or future-them) will find it. Include a one-paragraph context note: why the work happened, what it solved, who decided what.
What did you cut from scope, push to next time, or punt? Write each as a ticket / todo / note with enough context that someone (or you in 3 months) could pick it up cold.
For pieces over 1 week of work, write 3 lines: what went well, what didn't, what you'd do differently. Even just for yourself.
If someone external benefits from knowing this is done (a customer, a partner, a stakeholder), send the message. Brief, references the artifact, names what changes for them.
Mark the ticket / project / doc closed. Resist re-opening for "one more thing" — that goes in deferrals.
Return to Stage 3 when, while writing the retro, you realize a deferral you missed.
Input: Just finished a 3-week migration project.
Output:
Stage 1: Sent handoff to ops team — link to runbook, one-line summary, the 3 things they should know. Stage 2: Archived migration scripts and decisions doc to /projects/2026-q2-migration/. Added context note: why we migrated, what we considered, who decided. Stage 3: 4 deferrals captured as tickets: monitoring backfill, customer comms for stragglers, post-migration audit, decommission of old infra. Stage 4: Retro written: rollout was smoother than expected (good prep), but customer comms were rushed (start earlier next time). Stage 5: Sent customer-facing email to affected accounts. Stage 6: Project marked closed. Open tickets are explicit deferrals, not loose ends.
