Skip to content

bruce48x/Lakona / .agents/skills/lakona-doc-maintenance

lakona-doc-maintenance

Verified

Audit Lakona contributor documentation and report findings, or apply authorized cleanup to stale plans, duplicate authorities, and documentation maps within the requested scope.

FileKindSize
SKILL.mdskill md3.5 KB
agents/openai.yamlconfig281 B
references/audit-checklist.mdmarkdown4.0 KB
references/classification.mdmarkdown1.8 KB
references/operations.mdmarkdown3.6 KB

references/classification.md

View on GitHub
## Classification

Classify every relevant doc before editing:

- **Current authority:** defines active workflow, package boundaries, runtime
  contracts, validation rules, or architecture.
- **Current supplement:** explains a current subsystem but is not an entry point.
- **User-facing:** belongs to `README.md`, package README files, samples, or blog.
- **Stale plan:** task list, implementation plan, roadmap, or phase document for
  work that has already landed.
- **History-only:** explains removed frameworks, migration mechanics, old package
  names, or old starter designs without current operational value.
- **Duplicate:** repeats content already covered by a clearer current authority.

Default dispositions to propose during an audit, or apply during authorized cleanup:

- Keep current authority and current supplements.
- Apply the entrypoint's user-facing scope rule: repair links affected by the
  authorized cleanup, but rewrite user-facing content only when requested.
- Delete stale plans and history-only docs.
- Merge only durable current rules from duplicates into the active authority,
  then delete the duplicate.

## Lakona-Specific Rules

- `CONTRIBUTING.md` should be a concise contributor entry point, not a full
  architecture manual.
- `CONTRIBUTING.md` documentation maps should link only current authoritative
  docs.
- Do not preserve removed framework branding, old package names, or migration
  history in current docs unless there is an active compatibility reason.
- Do not create a new archive bucket just to save old decisions.
- If a historical decision still matters, rewrite it as a current rule in the
  relevant authority document.
- Move valuable content from `docs/superpowers/**` into permanent `docs/**`
  documentation, then clean up `docs/superpowers/**`.
- Remove empty archive directories after deleting their contents.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall