Skip to content
Skills Library
Documents & office · Writing

structured-writing

/structured-writing

Produces structured technical prose with clear hierarchy, scannable sections, and purposeful formatting. Use this skill when drafting specs, ADRs, or multi-section explanations that need consistent structure. Do not use when/for extreme brevity alone (use concise-output) or full article narrative arcs (use spine-framework).

Licence
MIT
Last repository change
30.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Produces structured technical prose with clear hierarchy, scannable sections, and purposeful formatting. Use this skill when drafting specs, ADRs, or multi-section explanations that need consistent structure. Do not use when/for extreme brevity alone (use concise-output) or full article narrative arcs (use spine-framework).

Original author description

Produces structured technical prose with clear hierarchy, scannable sections, and purposeful formatting. Use this skill when drafting specs, ADRs, or multi-section explanations that need consistent structure. Do not use when/for extreme brevity alone (use concise-output) or full article narrative arcs (use spine-framework).

How it works

  1. Critical rules
  2. Workflow
  3. Resources
  4. Validation
  5. Constraints
Original SKILL.md headings · 36 lines, 208 words
SKILL.md preview
---
name: structured-writing
description: >-
  Produces structured technical prose with clear hierarchy, scannable sections,
  and purposeful formatting. Use this skill when drafting specs, ADRs, or
  multi-section explanations that need consistent structure. Do not use when/for
  extreme brevity alone (use concise-output) or full article narrative arcs (use
  spine-framework).
version: 1.2.0
---

# Structured Writing

## Critical rules

- User dictates; tool structures. No large autonomous meaning/voice/content changes without asking.
- Small edits that capture intent execute directly; large rewrites/moves get proposed first.
- Frame gaps as completeness questions, never as domain expertise or advice.
- Preserve the author's voice. Never add substantial content they did not provide.
- No first-person tool voice, no praise.
- Before choosing a template or drafting examples, read [references/templates-and-examples.md](references/templates-and-examples.md).

## Workflow

1. Offer a workflow: structure first, discuss→draft→iterate, or draft first.
2. Capture dictation; organize into sections; apply formatting.
3. Propose (do not impose) large structural or wording changes.
4. Surface gaps as completeness questions; apply document template for the type.
5. For spoken dictation: propose cleanup of filler, repetition, verbosity.

## Resources

- [references/templates-and-examples.md](references/templates-and-examples.md) — document templates, voice rules, gap phrasing, examples. Read when structuring or cleaning dictation.

## Validation

- [ ] Small edits executed; large changes proposed
- [ ] Author voice preserved; no unprovided content added
- [ ] No asserted domain expertise; gaps are completeness questions
- [ ] No first-person or praise in tool responses

## Constraints

- In scope: structure, clarity, completeness, formatting. Out of scope: ideas, opinions, recommendations, subject-matter expertise.
- Related: `documentation-standards`, `system-architecture`, `data-visualization`, `concise-output`.
Files in this package (2)
  • SKILL.md 2 KB
  • references/templates-and-examples.md 2 KB

Versions

RepositoryScoreLicence
This page · jagreehal/jagreehal-claude-skills100MIT
viktorbezdek/skillstack100MIT

Database snapshot: 13.11.2026 · package version 987a83a42548 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100concise-output
    Enforces extreme brevity and high signal-to-noise so every word justifies its existence. Use this skill when writing any response, commit message, PR description, README, plan, or status update, or when output drifts into filler preambles. Do not use when/for long-form articles…
  • 100writing-scannable-prose
    Use when writing or revising a human-facing technical document — README, guide, ADR, PR description, changelog — or when asked to tighten, shorten, or declutter one ("tighten this", "too long", "hard to scan", "make this scannable"). Separates what the reader's decision depends…
  • 90spine-framework
    Structures long-form technical articles with the SPINE narrative framework for clarity and retention. Use this skill when writing or restructuring essays, deep-dives, or tutorial articles. Do not use when/for short README/API docs (use documentation-standards) or Agent Skill…
  • 90technical-writing-guide
    Use when structuring or rewriting standalone technical explanations, reports, status updates, documentation, recommendations, or operational handoffs so readers see the outcome, decision, action, or status first. Triggers on bottom line up front, BLUF, outcome-first writing,…
  • 100writing-technical
    Write clear technical documents — design docs, PR descriptions, proposals, postmortems — that lead with the decision and ground every claim in specifics. Use when drafting or editing workplace technical writing where a reader must act or later understand why. For the specific…
  • 100documentation-authoring
    Create structured docs from scratch — PRDs, technical specs, design docs, decision records, knowledge bases. Use when drafting documentation, writing proposals, defining requirements, or planning features.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.