drafting-stage-prompt

Writes curated stage prompt entries to a prompt library with win, loss, and update modes.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill drafting-stage-prompt-jin9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: drafting-stage-prompt
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/drafting-stage-prompt
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill drafting-stage-prompt-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams running multi-stage AI agent workflows lose hard-won prompt knowledge when successful or failed prompts are never captured. This Skill standardizes how prompts are saved into a structured prompt library so the Friday prompt-review ritual produces consistent, reusable entries instead of ad-hoc notes. ## Core Features & Use Cases - Win-mode entries: Writes a full library entry at prompts/library/<stage>/<topic>.md with verbatim prompt body, why-it-works paragraph, success metric, failure mode, model affinity, and invocation example. - Loss-mode anti-patterns: Appends a one-line failure note to prompts/library/_anti-patterns.md so losing prompts stay cheap to record and easy to avoid later. - Update mode and overwrite protection: Appends dated update blocks to existing entries and refuses to overwrite files without explicit confirmation, offering a -v2 variant instead. - Use Case: After a planning workflow where a Codex prompt produced a perfect step-by-step plan, tell the agent to save the prompt; it validates the stage and slug, drafts the entry from the template, and writes prompts/library/plan/jwt-validation.md ready to commit. ## Quick Start Ask the agent to save the prompt that just worked as a win entry for the plan stage under the topic jwt-validation in the prompt library.

Frequently Asked Questions about drafting-stage-prompt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save a prompt to a prompt library after a workflow run?▼

Tell the agent to save the prompt as a library entry, providing the stage (research, plan, critique, implement, review, or test), a kebab-case topic slug, the verbatim prompt body, and why it worked. The skill writes a templated entry to prompts/library/<stage>/<topic>.md.

What should a good prompt library entry contain?▼

A complete entry includes frontmatter with stage, topic, model affinity, and last-validated date, plus the verbatim prompt body, a why-it-works paragraph, a one-line success metric, a one-line failure mode, and an invocation example showing how the runner loads it.

Can I record prompts that failed instead of succeeded?▼

Yes. Loss mode appends a single dated line to prompts/library/_anti-patterns.md with the stage, topic slug, and a concrete reason for the failure. It deliberately avoids creating a full entry so losses stay cheap to capture.

What happens if the library entry file already exists?▼

The skill refuses to overwrite without explicit confirmation. It prints a diff of the existing entry and asks whether to overwrite, save as a -v2 variant, or abort, protecting historic entries from accidental loss.

When should I not use this prompt-curation skill?▼

Do not use it to edit repo-policy files like AGENTS.md or CLAUDE.md, to save prompts outside prompts/library/, or to write workflow postmortems. Profile prefix prompts belong to profile authoring, and postmortems use a separate skill.