quill: add quick-draft skill artifact
This commit is contained in:
1 parent
a6a3b17191
commit
44da73e010
1 file changed
+59
@@ -0,0 +1,59 @@
|
||||
---
|
||||
name: quick-draft
|
||||
description: Turn a topic into a structured prose draft in one pass.
|
||||
lane: Draft
|
||||
---
|
||||
|
||||
# quick-draft
|
||||
|
||||
Generate a complete first-draft document from a single topic sentence.
|
||||
|
||||
## When to Use
|
||||
|
||||
- User provides a subject and asks for a draft.
|
||||
- A skeleton exists and needs flesh.
|
||||
- Time-to-words matters more than polish.
|
||||
|
||||
## Protocol
|
||||
|
||||
1. Restate the topic as a one-line claim.
|
||||
2. List 3–5 supporting points as bullets.
|
||||
3. Expand each bullet into a short paragraph (2–4 sentences).
|
||||
4. Write a one-sentence conclusion that echoes the claim.
|
||||
5. Review for filler words; cut adjectives that don't carry weight.
|
||||
|
||||
Do not iterate. Ship the first complete pass.
|
||||
|
||||
## Template
|
||||
|
||||
Claim: [one sentence]
|
||||
|
||||
Support:
|
||||
- [point 1]
|
||||
- [point 2]
|
||||
- [point 3]
|
||||
|
||||
Body:
|
||||
[paragraph per point]
|
||||
|
||||
Conclusion:
|
||||
[one sentence]
|
||||
|
||||
## Example
|
||||
|
||||
Claim: Remote work improves output when async communication is enforced.
|
||||
|
||||
Support:
|
||||
- Fewer interruptions preserve deep work blocks.
|
||||
- Written updates create a searchable decision log.
|
||||
- Flexible schedules align work with personal peak hours.
|
||||
|
||||
Body:
|
||||
Deep work requires uninterrupted focus. Open-plan offices and back-to-back meetings fragment attention, making complex tasks take longer. When teams default to async updates, workers can batch communication and protect large blocks of time for execution.
|
||||
|
||||
Written updates replace live status meetings. Every decision and its reasoning gets recorded in a shared log, which becomes a knowledge base rather than a transient verbal exchange. New members can read the history instead of scheduling onboarding calls.
|
||||
|
||||
Flexible schedules let people work when they are most alert. Early risers ship before noon; night owls solve hard problems after dark. The team only needs overlap windows for collaboration, not synchronized 9-to-5 presence.
|
||||
|
||||
Conclusion:
|
||||
Remote work with enforced async communication raises output by protecting focus, building institutional memory, and letting individuals work at their peak.
|
||||
Reference in new issue
Block a user