How do I install the Ns Docs Writer skill?

Run npx skillmds@latest add nextstage-brasil/ns-docs-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ns Docs Writer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ns Docs Writer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ns Docs Writer free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Ns Docs Writer?

nextstage-brasil (@nextstage-brasil) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ns Docs Writer by nextstage-brasil — Agent Skill

Name: Ns Docs Writer
Author: nextstage-brasil

Ns Docs Writer

(NS) Human-facing project docs — README, docs/ guides, runbooks, contributor markdown. Use whenever the user asks for documentation, README updates, how-to guides, or docs/ content — even if they say "explain how to use" instead of "write docs". Do NOT use for code comments, API docblocks, requirements.md, or SDD version artifacts (use PM skills).

nextstage-brasil a3644f7 3 files · 4.6 KB Updated Sep 17, 2026

File contents

Docs Writer

Author clear, maintainable project documentation under docs/ and README files.

Session boot

See ../../ns-harness/references/session-boot.md.

Scope

In scope	Out of scope
`README.md` at product or repo root	Inline `//` or `/**` code comments
`docs/*/.md` guides	`docs/versions//sdd/requirements.md`, `docs/versions//requirements.md` (legacy SDD)
Runbooks, install guides, architecture overviews for humans	Living specs in `docs/specs/` (use `ns-living-spec`)
Changelog entries when requested	Marketing copy outside repo

When to use

New feature needs user or developer documentation
README is stale after structural changes
Onboarding guide for contributors
Consolidating scattered notes into docs/

Workflow

Discover — list existing docs/, README, and AGENTS.md links; avoid duplicating harness/brownfield artifacts (link instead).
Audience — confirm developer vs operator vs end-user (default: developer).
Outline — short TOC before drafting long guides.
Draft — follow references/style-guide.md.
Link — prefer relative links; point to canonical rules in .nextstage-harness/rules/ when relevant.

Layout (stack-agnostic)

Do not assume monorepo packages/ layout. Infer from:

AGENTS.md layout table
architecture-rules.md
Existing docs/ structure

Create subfolders only when they match project convention.

Integration

When called from ns-spec-driven, document delivered behavior — do not invent requirements.

Agent why (reference architecture, agent vs code, trade-offs, topology, HITL, change signal) lives in docs/specs/agent-architecture.md. Link it. Do not copy the interview or rewrite the decision record in README. docs/specs/agent.md is behavior (ns-living-spec), not this ADR.

Forbidden

Copying full bodies of brownfield-map.md or system-reverse-spec.md into new docs (link them)
English violations when project mandates English docs
Auto-generating docs for code that does not exist yet
Same version with both docs/versions/*/sdd/requirements.md and legacy docs/versions/*/requirements.md — link canonical sdd/ path only; never create or maintain dual trees

---name: ns-docs-writerdescription: (NS) Human-facing project docs — README, docs/ guides, runbooks, contributor markdown. Use whenever the user asks for documentation, README updates, how-to guides, or docs/ content — even if they say "explain how to use" instead of "write docs". Do NOT use for code comments, API docblocks, requirements.md, or SDD version artifacts (use PM skills).license: Apache-2.0---# Docs WriterAuthor **clear, maintainable** project documentation under `docs/` and README files.## Session bootSee `../../ns-harness/references/session-boot.md`.## Scope| In scope | Out of scope || -------- | ------------ || `README.md` at product or repo root | Inline `//` or `/**` code comments || `docs/**/*.md` guides | `docs/versions/*/sdd/requirements.md`, `docs/versions/*/requirements.md` (legacy SDD) || Runbooks, install guides, architecture overviews for humans | Living specs in `docs/specs/` (use `ns-living-spec`) || Changelog entries when requested | Marketing copy outside repo |## When to use- New feature needs user or developer documentation- README is stale after structural changes- Onboarding guide for contributors- Consolidating scattered notes into `docs/`## Workflow1. **Discover** — list existing `docs/`, README, and `AGENTS.md` links; avoid duplicating harness/brownfield artifacts (link instead).2. **Audience** — confirm developer vs operator vs end-user (default: developer).3. **Outline** — short TOC before drafting long guides.4. **Draft** — follow `references/style-guide.md`.5. **Link** — prefer relative links; point to canonical rules in `.nextstage-harness/rules/` when relevant.## Layout (stack-agnostic)Do not assume monorepo `packages/` layout. Infer from:- `AGENTS.md` layout table- `architecture-rules.md`- Existing `docs/` structureCreate subfolders only when they match project convention.## IntegrationWhen called from `ns-spec-driven`, document **delivered behavior** — do not invent requirements.Agent **why** (reference architecture, agent vs code, trade-offs, topology, HITL, change signal) lives in `docs/specs/agent-architecture.md`. Link it. Do not copy the interview or rewrite the decision record in README. `docs/specs/agent.md` is behavior (`ns-living-spec`), not this ADR.## Forbidden- Copying full bodies of `brownfield-map.md` or `system-reverse-spec.md` into new docs (link them)- English violations when project mandates English docs- Auto-generating docs for code that does not exist yet- Same version with both `docs/versions/*/sdd/requirements.md` and legacy `docs/versions/*/requirements.md` — link canonical `sdd/` path only; never create or maintain dual trees

Frequently asked questions