draft-piece

Draft and correct articles from briefs with verified code and reader-question checks.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/hkw2028/toy-project --skill draft-piece-hkw2028
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-piece
Source: https://github.com/hkw2028/toy-project/tree/main/.agents/skills/draft-piece
Command: npx skills add https://github.com/hkw2028/toy-project --skill draft-piece-hkw2028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing technical articles from a brief often drifts from the agreed thesis, ships unverified code examples, and loses confirmed style feedback between sessions. This Skill drafts or corrects a piece strictly against its brief contract, executes every embedded command, and preserves reusable writing criteria in shared repository files. ## Core Features & Use Cases - Brief-driven drafting: Writes section by section from a docs/briefs/SLUG/ brief, honoring the publication file's location, voice, and scope boundaries, and stops when a change would alter the thesis. - Two-layer verification: Hands the draft and reader questions to a fresh-context agent, and reruns every marked code block in the repository to confirm stated outputs match real results. - Feedback preservation: Records confirmed reusable writing rules in docs/decisions/ with rationale, scope, and accepted examples, while keeping one-piece exceptions local. - Use Case: Run it on docs/briefs/monorepo-move/ to produce the article at the publication's content path, verify its shell commands actually run, preview the rendered page locally, and hand off without committing. ## Quick Start Use the draft-piece skill to write the article from docs/briefs/my-topic/ and preview it locally.

Frequently Asked Questions about draft-piece

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

FAQPage Schema
How do I draft an article from a brief folder?

Point the skill at a docs/briefs/SLUG/ folder containing brief.md. It reads the brief, the named publication file, and glossary, then writes the piece section by section at the content location the publication defines.

How does it verify code examples in an article?

Every code block and command the brief marks is executed in the repository at writing time, and the stated output must match the real output. Blocks that cannot run are recorded as failed gates and the piece stays incomplete.

Can it correct an existing article that has no brief?

Yes. It treats the article plus your explicit correction as the bounded contract, preserves unaffected content and meaning, and reports that the full brief-based reader-question check did not run.

What happens when a request would change the article's thesis?

It stops instead of drafting. The current draft and evidence are preserved, the exact decision is stated, and the brief is returned to you for resettling, since drafting authority does not cover thesis or scope changes.

Where is confirmed writing feedback stored?

Reusable style and structure rules go into the relevant subject under docs/decisions/ with rule, reason, scope, and accepted examples. One-piece exceptions stay with the piece and never replace standing defaults.

Does it commit or publish the finished draft?

No. It stops before committing, opening a pull request, or publishing. Those steps happen after you read the draft, through the repository's Git skills or your own commands.