Produce draft-only evidence-backed technical behavior as sequence, activity, state-machine, and event-flow documentation. Do not use for business use-case catalogs, API contracts, or persistent data models.
source snapshot Aug 15, 2026
Topic / 13 skills
Source-linked DevKit workflows classified under documentation.
| Skill / purpose | Topics | Snapshot | Files |
|---|---|---|---|
| hi-behavior-modeling Produce draft-only evidence-backed technical behavior as sequence, activity, state-machine, and event-flow documentation. Do not use for business use-case catalogs, API contracts, or persistent data models. baka3k/dev-kit Mainverified | Aug 15, 2026 | 4 | |
| hi-data-model-discovery Produce draft-only evidence-backed physical and logical data models, ERDs, entity and field inventories, data dictionaries, ownership, read/write access, lifecycle, sensitivity, caching, replication, and migration gaps. Do not execute schema migrations or present inferred relationships as declared constraints. baka3k/dev-kit Mainverified | Aug 15, 2026 | 4 | |
| hi-docs-seeker Find current, authoritative technical documentation for libraries, frameworks, APIs, tools, standards, versions, migrations, configuration, and compatibility. Use when an answer requires verified external documentation or precise source links. baka3k/dev-kit Mainverified | Aug 15, 2026 | 5 | |
| hi-document-lifecycle Orchestrates evidence-backed document generation, human clarification, semantic/diagram refinement, and conditional review-comment resolution with pause/resume for one scoped domain. Use hi-maintenance-docs for a complete multi-domain pack. baka3k/dev-kit Mainverified | Aug 15, 2026 | 6 | |
| hi-document-refinement Analyze an evidence-backed draft for ambiguity, terminology gaps, missing semantics, and under-specified Mermaid diagrams, then apply validated clarification answers to an isolated candidate revision. Do not generate initial documents, resolve review comments, invent answers, or update an orchestrator's global manifest. baka3k/dev-kit Mainverified | Aug 15, 2026 | 5 | |
| hi-document-review-resolution Resolve structured review comments against an evidence-backed document revision; assign a disposition to every comment and apply accepted changes idempotently. Do not generate, clarify, approve publication, or update global manifests. baka3k/dev-kit Mainverified | Aug 15, 2026 | 4 | |
| hi-log Write log entries analyzing recent changes and session reflections. baka3k/dev-kit Mainverified | Aug 15, 2026 | 2 | |
| hi-maintenance-docs Orchestrate a complete, navigable, evidence-backed maintenance documentation pack spanning system overview, architecture, modules, use cases, technical behavior, API contracts, data models, command specifications, gaps, and freshness. Use for end-to-end documentation — not one bounded domain. baka3k/dev-kit Mainverified | Aug 15, 2026 | 9 | |
| hi-project-organization Organize project files, directories, output paths, names, and Markdown structure. Use when creating files, choosing where outputs belong, reorganizing existing assets, or standardizing a project layout. baka3k/dev-kit Mainverified | Aug 15, 2026 | 4 | |
| hi-repo-recon Map an unfamiliar repository into an evidence-backed module inventory, entry-point map, and optional key-function catalog. Use for repository onboarding, architecture reconnaissance, handover preparation, or refactor scoping. baka3k/dev-kit Mainverified | Aug 15, 2026 | 3 | |
| hi-repository-search Gather traceable evidence from repository code and project documents. Use for codebase exploration, architecture, feature tracing, dependency or impact analysis, and questions that require verified source context. baka3k/dev-kit Mainverified | Aug 22, 2026 | 3 | |
| hi-repowiki Generate or update a comprehensive, evidence-backed repository wiki in Repo Wiki format (/repowiki/), including architecture, installation and configuration, CLI/build automation, languages and frameworks, data/graph schemas, protocol integrations such as MCP, query/search, incremental processing, APIs, testing, deployment, developer guidance, troubleshooting, module documentation, and knowledge cards. Use for codebase documentation, team onboarding, repository capability mapping, and persistent architecture knowledge. baka3k/dev-kit Mainverified | Aug 15, 2026 | 7 | |
| hi-tech-build-audit Audit a repository's technology stack, build system, dependency management, CI/CD pipelines, deployment targets, and platform assumptions. Use for build onboarding, migration readiness, deployment review, or CI/CD documentation. baka3k/dev-kit Mainverified | Aug 15, 2026 | 3 |
Produce draft-only evidence-backed technical behavior as sequence, activity, state-machine, and event-flow documentation. Do not use for business use-case catalogs, API contracts, or persistent data models.
source snapshot Aug 15, 2026
Produce draft-only evidence-backed physical and logical data models, ERDs, entity and field inventories, data dictionaries, ownership, read/write access, lifecycle, sensitivity, caching, replication, and migration gaps. Do not execute schema migrations or present inferred relationships as declared constraints.
source snapshot Aug 15, 2026
Find current, authoritative technical documentation for libraries, frameworks, APIs, tools, standards, versions, migrations, configuration, and compatibility. Use when an answer requires verified external documentation or precise source links.
source snapshot Aug 15, 2026
Orchestrates evidence-backed document generation, human clarification, semantic/diagram refinement, and conditional review-comment resolution with pause/resume for one scoped domain. Use hi-maintenance-docs for a complete multi-domain pack.
source snapshot Aug 15, 2026
Analyze an evidence-backed draft for ambiguity, terminology gaps, missing semantics, and under-specified Mermaid diagrams, then apply validated clarification answers to an isolated candidate revision. Do not generate initial documents, resolve review comments, invent answers, or update an orchestrator's global manifest.
source snapshot Aug 15, 2026
Resolve structured review comments against an evidence-backed document revision; assign a disposition to every comment and apply accepted changes idempotently. Do not generate, clarify, approve publication, or update global manifests.
source snapshot Aug 15, 2026
Write log entries analyzing recent changes and session reflections.
source snapshot Aug 15, 2026
Orchestrate a complete, navigable, evidence-backed maintenance documentation pack spanning system overview, architecture, modules, use cases, technical behavior, API contracts, data models, command specifications, gaps, and freshness. Use for end-to-end documentation — not one bounded domain.
source snapshot Aug 15, 2026
Organize project files, directories, output paths, names, and Markdown structure. Use when creating files, choosing where outputs belong, reorganizing existing assets, or standardizing a project layout.
source snapshot Aug 15, 2026
Map an unfamiliar repository into an evidence-backed module inventory, entry-point map, and optional key-function catalog. Use for repository onboarding, architecture reconnaissance, handover preparation, or refactor scoping.
source snapshot Aug 15, 2026
Gather traceable evidence from repository code and project documents. Use for codebase exploration, architecture, feature tracing, dependency or impact analysis, and questions that require verified source context.
source snapshot Aug 22, 2026
Generate or update a comprehensive, evidence-backed repository wiki in Repo Wiki format (/repowiki/), including architecture, installation and configuration, CLI/build automation, languages and frameworks, data/graph schemas, protocol integrations such as MCP, query/search, incremental processing, APIs, testing, deployment, developer guidance, troubleshooting, module documentation, and knowledge cards. Use for codebase documentation, team onboarding, repository capability mapping, and persistent architecture knowledge.
source snapshot Aug 15, 2026
Audit a repository's technology stack, build system, dependency management, CI/CD pipelines, deployment targets, and platform assumptions. Use for build onboarding, migration readiness, deployment review, or CI/CD documentation.
source snapshot Aug 15, 2026