pyramid-long-form
Drafts or restructures a multi-section document (report, brief, proposal, whitepaper, strategy doc, research writeup) using the Pyramid Principle. Use when the user wants a new document built or an existing one reorganized. Not for critiquing a draft without rewriting it; use `pyramid-audit` instead. Not for single-page notes under 500 words; use `pyramid-short-form` instead.
tyroneross · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add tyroneross/pyramid-principle --skill pyramid-long-form技能说明
name: pyramid-long-form
description: Drafts or restructures a multi-section document (report, brief, proposal, whitepaper, strategy doc, research writeup) using the Pyramid Principle. Use when the user wants a new document built or an existing one reorganized. Not for critiquing a draft without rewriting it; use pyramid-audit instead. Not for single-page notes under 500 words; use pyramid-short-form instead.
user-invocable: false
Pyramid Long-Form
Purpose
Structure or draft a multi-section professional document. Load pyramid-principle-core for structure and direct language. Add a pyramid-source-integrity check when facts or data materially affect the output; receive a claim packet only when strict trace mode applies.
This skill handles documents that require developed sections or usually exceed about 500 words. It does not audit existing writing or produce slide storylines.
Route the Request
Use this skill for reports, briefs, proposals, research writeups, decision documents, strategy documents, and whitepapers.
Hand off when:
- the artifact is an email, Slack update, executive summary, or one-pager →
pyramid-short-form - the artifact is a deck or presentation storyline →
pyramid-presentation - the user wants existing writing diagnosed →
pyramid-audit - the user wants the framework explained →
pyramid-principle-core
Identify the Inputs
Before structuring the document, the agent identifies:
- Reader question: What must the document answer?
- Governing thought: Which decision, recommendation, or finding did the user supply?
- Cleared claims: When source integrity applies, which facts, calculations, inferences, recommendations, and limitations may the document use, and what source, locator, confidence, and reason accompany each data point?
- Requested depth: Outline, detailed outline, section draft, or full document?
- Constraints: Audience, length, tone, required sections, sensitivity, and citation format.
The agent asks a question only when a missing answer would materially change the document and the supplied evidence does not support a safe choice.
Return the Requested Depth
- Outline: Return the title, actual decision or governing claim, section claims, and nested source-backed supports. The eventual document word budget does not set the outline's length. Do not draft body prose or output framework commentary.
- Detailed outline: Add subsection claims, evidence placement, and source notes.
- Section draft: Draft only the requested section and preserve its position in the document logic.
- Full document: Draft the complete document after the outline passes the internal checks.
Do not output SCQA, key-line, reasoning-mode, assumption, or self-check labels unless the user requests an annotated structure.
When the user requests a source-bound outline or says to use only supplied facts:
- build only from the claim set and evidence limits cleared by
pyramid-source-integrity; - omit generic introduction, implementation, expected-outcome, and conclusion sections unless the user requests them and the cleared claim set supplies their content;
- do not add a section merely because it is common in that document type;
- place a requested but unverified expected result under
Evidence limits, not in the storyline as a prediction.
The source-bound outline starts with the actual title and decision sentence, then uses only asserted section headings with their supplied facts. It may end with one Evidence limits section. It must not print the drafting labels Title, Governing Thought, Fact, Inference, Decision, Rationale, or End of Outline.
Unless the cleared claim set supplies their content, the agent must not create sections named or serving as Introduction, Implementation, Expected Outcomes, Benefits, Next Steps, or Conclusion.
If the cleared decision includes an intervention whose effect remains unverified, state the intervention in the decision sentence only. Put the missing outcome evidence under Evidence limits rather than creating a benefits section.
Use this final syntax for a source-bound outline:
- first line: a Markdown
#title with noTitlelabel; - second paragraph: the supplied decision sentence with no
Governing Thought,Governing Claim, orDecisionlabel; - remaining
##sections: source-backed claims and their supplied facts; - optional final
## Evidence limitssection; - stop after the final section without an
End of Outlinelabel.
Build the Architecture
The agent completes the architecture before drafting prose:
- Write the governing thought. Use the decision, recommendation, or finding cleared for use. Do not replace it with a stronger outcome claim.
- Add only necessary introduction context. Include the minimum Situation or Complication the reader needs, then state the governing thought before the document body. When the context is shared, begin with the governing thought. (
minto-p22-scqa) - Select section claims. Use the distinct claims required to support the governing thought. Do not add or remove sections to reach a preferred count.
- Test each peer set. Every section or subsection at one level answers the same parent question and performs the same logical role. Different topics may remain peers when one accurate role label describes all of them. (
minto-p96-mece) - Choose one order per peer set. Use deductive, chronological, structural, or comparative order only when the material shows that order. (
minto-p5-pyramid-sorting,minto-p63-deduction-induction) - Place evidence under the claim it supports. Do not create a separate background or data section when the material belongs under a specific claim.
- Nest only when needed. Add a lower level when a section claim requires multiple distinct supports. Do not create depth to make the outline look complete.
Draft the Prose
When the use
阅读完整来源 ↗