tech-outline-planner
Skill87 starsChanged 6 months agoApache-2.0View on GitHub
Generates high-quality technical article outlines using a combined narrative structure (Context-first & Process narrative). Invoke when planning, structuring, or refactoring technical articles, system designs, or AI architecture posts.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-skill-reviewerSkill
- code-readerSkill
- dir-organizerSkill
- doc-reviewerSkill
- drawio-designerSkill
- editorial-card-designerSkill
- humanizer-zhSkill
- md-link-checkerSkill
- md-summarizerSkill
- md-translatorSkill
- ontologySkill
- openspec-assistantSkill
- pptx-editorSkill
- pptx-readerSkill
- project-analyzerSkill
- reference-organizerSkill
- self-reviewSkill
- update-submitterSkill
- web-content-downloaderSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When generating an outline, follow this structure to ensure both clarity and depth:
- Distinctive: line 25
When explaining the "Solution", embed a logical sequence that guides the reader through concepts naturally.
- Distinctive: line 27
Logical Transitions: Ensure each concept flows naturally into the next, like a movie montage.
- Distinctive: line 28
"Given before New" Principle: Always start a sentence or section with information already established ("Given") before introducing "New" …
- Distinctive: line 36
When the user provides a technical topic and asks for an article outline.
- Distinctive: line 37
When an existing draft lacks a clear logical flow or technical depth.
- Distinctive: line 38
When planning complex system design documentation.
- Distinctive: line 44
Deep Dive into Solution: Use Process Narrative to break down the technical components.
- Distinctive: line 50
No Bilingual Titles: Use only one language for titles (Chinese).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Technical Outline Planner
This skill helps you design "Architecture Review Grade" technical article outlines. It employs a dual-layer narrative structure to balance macro understanding with technical depth.
1. Core Methodology: Combined Narrative Structure
When generating an outline, follow this structure to ensure both clarity and depth:
1.1 Outer Layer: Context-first (Classic Style)
Simulate an equal dialogue with the reader, presenting the truth transparently.
- Context: Establish the background and environment.
- Issue: Identify the specific problem or challenge being addressed.
- Solution: Propose the technical solution or architecture.
- Trade-off: Discuss the compromises, limitations, and decision-making rationale.
1.2 Inner Layer: Process Narrative
When explaining the "Solution", embed a logical sequence that guides the reader through concepts naturally.
- Logical Transitions: Ensure each concept flows naturally into the next, like a movie montage.
- "Given before New" Principle: Always start a sentence or section with information already established ("Given") before introducing "New" information. This creates an organic link between ideas.
2. Usage Instructions
2.1 Trigger Scenarios
- When the user provides a technical topic and asks for an article outline.
- When an existing draft lacks a clear logical flow or technical depth.
- When planning complex system design documentation.
2.2 Execution Steps
- Understand the Core Intent: Identify the target audience and the primary technical challenge.
- Apply Outer Structure: Map the topic to the Context → Issue → Solution → Trade-off framework.
- Deep Dive into Solution: Use Process Narrative to break down the technical components.
- Refine with "Given before New": Review the sequence of headings and sub-headings to ensure a smooth cognitive load transition.
2.3 Output Constraints
- Language: Output the final outline in Chinese.
- No Bilingual Titles: Use only one language for titles (Chinese).
- Introductory Paragraphs: Each chapter and sub-section MUST start with a brief, high-information density introduction (avoiding filler phrases like "This section will discuss...").
- Professional Tone: Maintain a rigorous, architecture-review style.
3. Reference Material
For detailed examples and deeper theoretical background on the narrative layers, refer to narrative-structure.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.