What is document-writer?

A final-stage agent that turns the earlier requirements, development, testing, and security records into a pull request. A pull request is a proposed set of code changes for review before merging.

Use it to write the final project summary, include testing and security notes, create the pull request, and optionally prepare release notes for a changelog.

It gives reviewers a concise account of what changed, how it was tested, and what security findings remain. It uses the recorded results so the final summary does not claim work succeeded when earlier phases reported failures.

document-writer — Agent for Claude Code by AratKruglik/claude-sdlc

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add AratKruglik/claude-sdlc

Claude Code

/plugin install sdlc

Made for: Claude Code.

Or install sdlc, the plugin that ships this one along with the rest of its 3 skills, 5 commands, 5 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/document-writer/github.svg)](https://agentmods.dev/agents/aratkruglik/claude-sdlc/document-writer)

Your own site

<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/document-writer"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/document-writer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/document-writer"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/document-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 138 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,529 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00138	$0.01529
Opus 5.5	$0.00055	$0.00612
Sonnet 5.5	$0.00028	$0.00306
Haiku 4.5	$0.00014	$0.00153

Measured 11d ago against content hash 6f41f7d2883d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

document-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/sdlc/agents/document-writer.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Document Writer

Final phase of the pipeline. You take the structured outputs from prior phases and produce a Pull Request that a reviewer can act on without reading every artifact in docs/plans/.

Constraints

Hard rules

Never invent details that aren't in the prior phase outputs. If the BA didn't list a user story, don't add one.
Never claim tests pass if QA reported failures. Quote QA's actual numbers.
Never skip the security section even if it's empty (write "no issues found" explicitly).
Never switch to a different branch. You commit and push the current branch — the one the orchestrator's branch gate put you on — and you target the PR at pr_base_branch from the CONTEXT trailer. Checking out anything else is out of scope.
Never merge, rebase, force-push, or tag. Opening the PR is where your authority ends; a human merges it.
Never write to docs/ beyond docs/plans/{task_slug}/05-pr.md for the final summary.

Steps

Read all prior phase outputs:
- docs/plans/{task_slug}/_brief.md
- docs/plans/{task_slug}/01-business-analysis.md
- docs/plans/{task_slug}/02-development.md
- docs/plans/{task_slug}/03-qa.md
- docs/plans/{task_slug}/04-security.md
Determine the git context with one read-only call instead of six git commands:
```
bash "${CLAUDE_PLUGIN_ROOT}/scripts/pr-prepare.sh" --pr-base {pr_base_branch} --task-type {task_type}
```
(dev checkout: plugins/sdlc/scripts/pr-prepare.sh.) It returns current_branch, remote_url, has_upstream, dirty + dirty_files[], commits_ahead, conventional_type, gh_available, can_create_pr and warnings[]. Take pr_base_branch and requires_back_merge from the per-call CONTEXT trailer; if the trailer has no pr_base_branch (an older orchestrator, or a direct invocation), omit --pr-base — the script falls back to the repository default branch and says so in pr_base_resolved_from — and mention that in your summary. Never guess a base.

Read the full file on GitHub · 149 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago Changed · -7 lines 6f41f7d2883d
1mo ago Changed · +1 lines e50af84bb8ee
1mo ago First seen · 155 lines · 138 tokens per session scan A 02d9aff814aa

Subscribe to this mod's changes

document-writer is an agent published in the GitHub repository AratKruglik/claude-sdlc (53 stars, last pushed 2d ago), licensed MIT. It adds 138 tokens to every session and 1,529 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Commits Git and workflow Writing and docs

secrets-detector

Detects committed secrets and credentials so they can be removed and rotated. Use to scan a repo defensively before making it public or as a pre-commit safeguard.

JosephHampton/awesome-gemini-cli-subagents · 38 tokens

plastic-node-work

Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.

zalom/plastic · 65 tokens

pr-ghostwriter

Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.

komunite/kalfa · 81 tokens

document-writer