# Tech Outline Planner

> 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.

- Skill: `forceinjection/tech-outline-planner` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add forceinjection/tech-outline-planner`
- Raw SKILL.md: https://api.skillmd.com/api/skills/forceinjection/tech-outline-planner/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ForceInjection (https://skillmd.com/u/forceinjection)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/forceinjection/tech-outline-planner

---


# 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

1. **Understand the Core Intent**: Identify the target audience and the primary technical challenge.
2. **Apply Outer Structure**: Map the topic to the Context → Issue → Solution → Trade-off framework.
3. **Deep Dive into Solution**: Use Process Narrative to break down the technical components.
4. **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](./references/narrative-structure.md).