# Engineering Writing

> Use for drafting or condensing software-engineering prose such as requirements/specs, READMEs, commits, PRs, runbooks, errors, and design notes. Not for general, academic, or Australian legal prose.

- **Type:** Skill
- **Install:** `agentstack add skill-mblauberg-provenant-engineering-writing`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [mblauberg](https://agentstack.voostack.com/s/mblauberg)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [mblauberg](https://github.com/mblauberg)
- **Source:** https://github.com/mblauberg/provenant/tree/main/skills/engineering-writing

## Install

```sh
agentstack add skill-mblauberg-provenant-engineering-writing
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Engineering writing

Write clear, brief, accurate and useful engineering prose in Australian English.
Cut first. Add only what serves the reader's job and belongs in this document.

This skill is a specialization of the `natural-writing` hub: it owns
codebase/README/commit/PR artefact types and links to the hub for the
Australian English default, the anti-AI taxonomy and the condense pass. See
`references/process.md`, `references/style-standard.md` and
`references/engineer-voice.md` for where each hub link applies.

## Workflow

1. Name the audience, prior knowledge, required action or decision, and format
   constraint. If the reader's job is unclear, flag it before drafting.
2. Choose one relevant pattern: [document patterns](references/document-patterns.md)
   for codebase/short-form prose, [requirements and planning](references/requirements-and-planning.md)
   for already-decided pre-build content, or [architecture and communication](references/architecture-and-presentations.md)
   for approved designs, ADRs, presentations and briefs. Do not load all three.
3. Structure before sentences: front-load the point, use decision-oriented
   headings and one idea or requirement per unit, then move wrong-home material.
4. Lock facts, logic, stance, evidence, obligations, behaviour, identifiers,
   paths, commands, flags, parameters, keys, error codes, numbers, units, dates,
   citations and quoted terms.
5. Revise in separate structure, accuracy, clarity/concision, voice and
   Australian-English passes. Load only the needed section from
   [process](references/process.md), [style standard](references/style-standard.md),
   [engineer voice](references/engineer-voice.md) or the `natural-writing`
   skill's Australian English default;
   use [sentence mechanics](references/strunk-mechanics.md) or
   [sources](references/sources.md) only for a specific problem. Load the hub
   anti-AI taxonomy and condense pass from the `natural-writing` skill
   alongside `engineer-voice.md` and `process.md` respectively.

Preserve technical meaning and evidence altitude. Distinguish observation from
interpretation; attach numbers to comparatives. Verify every package, API,
version, flag and URL against code or documentation, otherwise mark
`[FLAG: verify]`. Never invent facts to fill a document. Keep genuine caveats
and honest negatives while cutting padding, marketing language, AI tells,
instruction-leaking absence tombstones and internal process language from
reader-facing prose. Match existing repository conventions without copying
signature phrases.

For condensation, follow the reference stop and integrity checks and report the
before/after word delta. Review mode returns severity, evidence, impact and fix;
rewrite mode returns text first; final scrub makes defect fixes only.

For local files, use the checker as a review prompt, not proof:

```sh
python3 "${AGENTS_HOME:-$HOME/.agents}/skills/engineering-writing/scripts/check_engineering_style.py" path/to/file.md
```

Flag unverifiable support, audience dependence, domain-required terms, or a cut
that would drop an obligation. Use `[FLAG: verify source]`,
`[FLAG: define audience]`, `[FLAG: preserve exact term]` or
`[FLAG: shortening drops obligation]` where applicable. Do not smooth
uncertainty away.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [mblauberg](https://github.com/mblauberg)
- **Source:** [mblauberg/provenant](https://github.com/mblauberg/provenant)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-mblauberg-provenant-engineering-writing
- Seller: https://agentstack.voostack.com/s/mblauberg
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.