content-planner
Shape a writing task into an outline, brief, sequence, or publishable plan. Use when a content request needs structure (audience, goal, outline, success metric) before drafting.
- License 许可
- MIT
- 所属仓库
- Eliyce/paqad-ai
- 最近更新
- 2026-11-13
- Stars
- ★ 8
- Forks
- 0
01 前言 Front Matter
- name
- content-planner
- description
- Shape a writing task into an outline, brief, sequence, or publishable plan. Use when a content request needs structure (audience, goal, outline, success metric) before drafting.
02 资源文件 3
- 资产文件assets/brief.template.md505 B
- 参考文档references/planner-checklist.md588 B
- 脚本scripts/lint-brief.sh723 B
03 SKILL.md 正文
Content Planner
What It Does
Turns a broad content ask into a concrete brief that a writer can act on without re-asking the original requester for context.
Use This When
Whenever the next step would be drafting and the request lacks audience, goal, structure, or success metric.
Inputs
- The original request and any linked references.
references/planner-checklist.mdfor which fields a brief must contain.
Procedure
- Walk
references/planner-checklist.md(audience, goal, constraints, outline, dependencies, success metric); never skip a field silently. - Fill
assets/brief.template.mdwith project-specific values; mark unknowns explicitly. - Validate with
scripts/lint-brief.sh: exit 0 means every required field is present.
Output Contract
- Match
assets/brief.template.mdexactly. - Output must pass
scripts/lint-brief.sh.
Resources
references/planner-checklist.mdscripts/lint-brief.shassets/brief.template.md
04 同仓库更多 Skills
sample-skill
Sample bundled skill fixture
processing-invoices
Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.
processing-invoices
Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.
understand-idea
Chat and Claude Code: Step 1 of the discover journey: clarifies the goal, who benefits, success and constraints into the idea block. Use when the journey directs it to step 1, not directly.
size-work
Chat and Claude Code: Suggest a size for a ticket from comparable finished work, as a labelled suggestion the team still owns. Use it when someone asks "how big is this?", "roughly how much work is ABC-12?", or wants a backlog item sized. It finds the team's sizing scale at first use, picks two to five of the closest finished tickets with links, and gives a size or range with the drivers behind it and a confidence of low, medium or high, lowered and explained when the area's documents are template text. Every result is labelled a suggested size, never a date or a commitment. It writes nothing into the size field unless the user says "set it", and it refuses to overwrite an existing size unless the user asks to replace it. Produces the sizing block of the record.
refine-ticket
Chat and Claude Code: Improve one or more existing tracker tickets without losing the author's intent. Use it when someone wants a ticket read, diagnosed and tidied up ("this ticket is vague", "fix up ABC-12", "split this, it's too big"). It reads each ticket in full and snapshots it with its last-updated time, says what is wrong with evidence, and proposes a field-by-field before and after change set limited to summary, description, labels, parent, links and new child tickets on a split. It writes nothing until an explicit "apply it" bound to that exact change set, re-checks the ticket for conflicting edits just before writing, never replaces rich descriptions with plain text, never deletes or closes a ticket, and reads each ticket back after applying. Produces the existing and changes blocks of the record.