- Home
- Skills
- Jpicklyk
- Task Orchestrator
- Documentation Implementation
documentation-implementation_skill
- Kotlin
149
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill jpicklyk/task-orchestrator --skill documentation-implementation- SKILL.md10.8 KB
Overview
This skill provides domain-specific guidance and practical patterns for producing clear, accurate technical documentation, API references, and user guides. It focuses on validation, clarity standards, and examples that run. Use it to enforce documentation quality and reduce context loss when documenting features tied to persistent AI memory and developer tools.
How this skill works
The skill inspects task tags, existing docs, and implementation code to produce or validate documentation that matches real behavior. It offers validation commands for linting, spell-checking, link checking, and building or previewing documentation sites. It also provides success criteria, common patterns, blocker reports, and a quality checklist to complete documentation tasks reliably.
When to use it
- Creating or updating API references (endpoints, schemas, status codes)
- Writing user guides, tutorials, or README quick starts
- Validating documentation quality before release
- Documenting code, functions, or Kotlin-specific examples
- Preparing docs for workflow automation or persistent-memory features
Best practices
- Test examples and code snippets locally so they run without errors
- Start each doc with a concise overview and prerequisites
- Document inputs, outputs, edge cases, and authentication clearly
- Use linting, spell checks, and link checks as part of CI
- Keep sentences short, use active voice, and define terms on first use
Example use cases
- Produce an API endpoint page showing path, request body, responses, and curl examples
- Write a README with installation, quick start, configuration options, and contributing notes
- Create a user guide for enabling authentication or integrating persistent memory
- Validate a docs site build, fix broken links, and run a live preview
- Report blockers using the provided template when implementation or assets are missing
FAQ
Documentation must be accurate, complete, include working examples, have valid links, correct spelling/grammar, and follow the project style guide.
Which validation tools should I run before merging docs?
Run markdown linting, a spell checker, link checking, and, if applicable, build the docs site and preview it locally.
What if implementation details are missing or contradictory?
Test the feature, read the implementation, and if uncertainty remains, file a blocker report requesting clarification from a senior engineer.