ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
Claude Code
$ npx -y skills add yonatangross/orchestkit --skill documentation-patterns --agent claude-code
Codex
$ npx skills add yonatangross/orchestkit --skill documentation-patterns -a codex -y
Cursor
$ npx skills add yonatangross/orchestkit --skill documentation-patterns -a cursor -y
Gemini CLI
$ npx skills add yonatangross/orchestkit --skill documentation-patterns -a gemini-cli -y
GitHub Copilot
$ npx skills add yonatangross/orchestkit --skill documentation-patterns -a github-copilot -y
OpenCode
$ npx skills add yonatangross/orchestkit --skill documentation-patterns -a opencode -y
Windsurf
$ npx skills add yonatangross/orchestkit --skill documentation-patterns -a windsurf -y
name: documentation-patterns license: MIT compatibility: "Claude Code 2.1.277+." description: Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs. user-invocable: false context: inherit effort: low allowed-tools: "Read Glob Grep" metadata: version: "1.0.0" author: "OrchestKit" complexity: "low" tags: "documentation, readme, adr, api-docs, openapi, changelog, writing-style, technical-writing, ci-cd"
Templates and opinionated structures for technical documentation -- READMEs, Architecture Decision Records, OpenAPI specs, changelogs, and writing style. Each category has individual rule files in `rules/` loaded on-demand.
| Category | Rule | Impact | When to Use | |----------|------|--------|-------------| | [README](#readme) | 1 | HIGH | Starting a project, onboarding contributors | | [ADR](#architecture-decision-records) | 1 | HIGH | Recording architecture decisions | | [API Docs](#api-documentation) | 1 | HIGH | Documenting REST APIs with OpenAPI 3.1 | | [Changelog](#changelog) | 1 | MEDIUM | Maintaining release history | | [Writing Style](#writing-style) | 1 | MEDIUM | Any technical writing task |
**Total: 5 rules across 5 categories**
## README Skeleton # Project Name Brief description -> Quick Start -> Installation -> Usage -> API -> Config -> Contributing -> License ## ADR Format # ADR-001: Title Status -> Context -> Decision -> Consequences (positive/negative) -> References ## OpenAPI Minimum openapi: 3.1.0 with info, paths, components/schemas, error responses ## Changelog Entry ## [1.2.0] - 2026-03-05 ### Added / Changed / Deprecated / Removed / Fixed / Security ## Writing Rule of Thumb Active voice, present tense, second person, one idea per sentence
Complete README template with all essential sections for open-source and internal projects.
Structured format for capturing architectural decisions with context and consequences.
OpenAPI 3.1 specification patterns for consistent, machine-readable API docs.
Keep a Changelog format for curated, human-readable release history.
Technical writing conventions for clear, scannable documentation.
**Version:** 1.0.0 (March 2026)
The Complete AI Development Toolkit for Claude Code. 115 skills, 36 agents, 163 hooks. Install `ork` for stable (v10.x).
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request…
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request…
Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories, budgets,…
Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a…
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.