DataArt/artisyn-implementation-harness / skills/implementation-harness
implementation-harness
FlaggedInstall the portable AI-dev harness, rebuild its operational graph standalone, harvest project skill improvements into its canonical templates, package direct canonical edits into a portable bundle, or apply canonical updates to an existing project. Use /implementation-harness launch, /implementation-harness reindex-graph, or /implementation-harness patch harvest|prepare|apply.
canonical/agents/docs-writer/INTENT.md
View on GitHub---
skill: agents/docs-writer
output: {{provider:agents_root}}/docs-writer.{{provider:agent_extension}}
---
## Purpose
When adding, renaming or removing pages, verify existing documentation-site navigation
still resolves. This responsibility is conditional on a site configuration being
present; it does not require creating one.
Permanent doc writer invoked any time architecture or project docs need to be created or updated — during the design lifecycle's Publish stage, the dev lifecycle's Document stage, or any inline conversation. Reads the project's Documentation Principles article before writing, enforces diagram-first format with colored Mermaid, and applies the certainty principle. Checks the terminology registry before naming a concept and appends new project-specific terms it coins. Also maintains existing docs-site navigation when pages are added, renamed or removed.
## Substitutions
| Placeholder | Source | Notes |
| ---------------------------- | ------------------------------- | ------------------------------------------------------------- |
| `{{DOC_PRINCIPLES_ARTICLE}}` | Q — Doc Principles article path | e.g. `docs/Engineering Guide/Documentation/01 Principles.md` |
| `{{DOC_STRUCTURE_ARTICLE}}` | Q — Doc Structure article path | e.g. `docs/Engineering Guide/Documentation/02 Structure.md` |
| `{{TERMINOLOGY_REGISTRY}}` | Q — Terminology registry path | e.g. `docs/Engineering Guide/Documentation/07 Terminology.md` |
## Conditionals
None.
## Verify checklist
- [ ] `{{DOC_PRINCIPLES_ARTICLE}}` resolves to a file that exists in the project
- [ ] `{{DOC_STRUCTURE_ARTICLE}}` resolves to a file that exists in the project
- [ ] `{{TERMINOLOGY_REGISTRY}}` resolves to a file that exists in the project
- [ ] Agent description mentions it can be invoked from any phase (not just the Publish stage)
- [ ] Agent points to Core doc principles in `{{DOC_PRINCIPLES_ARTICLE}}` rather than restating diagram/coloring/certainty/length rules
- [ ] Agent checks `{{TERMINOLOGY_REGISTRY}}` before naming a concept and appends new project-specific terms rather than silently coining a synonym
- [ ] Output format (one-line summary per doc) is described
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |