Plan implementations, design architectures, create technical roadmaps with detailed phases.
source snapshot Aug 22, 2026
Topic / 09 skills
Source-linked DevKit workflows classified under architecture.
| Skill / purpose | Topics | Snapshot | Files |
|---|---|---|---|
| hi-plan Plan implementations, design architectures, create technical roadmaps with detailed phases. baka3k/dev-kit Mainverified | Aug 22, 2026 | 9 | |
| 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-module-summary-report Synthesize existing module-inventory and tech-audit artifacts into an architecture summary, per-module breakdown, risk assessment, and optional Mermaid diagrams. Do not inspect source from scratch or run full onboarding. baka3k/dev-kit Mainverified | Aug 15, 2026 | 2 | |
| hi-pptx Create, edit, and visually validate client-ready PowerPoint presentations (.pptx) using a sanitized navy-white-orange-teal design system, with evidence-led storylines, natural executive copy, editable architecture/process/timeline/option layouts, and professional native charts derived from supplied CSV, JSON, spreadsheet, or tabular data. Use for executive proposals, consulting decks, technical architecture, current-state assessments, phased roadmaps, investment options, KPI reviews, and Japanese-customer-facing presentations where visual consistency, quantitative accuracy, privacy, and presentation readiness matter. baka3k/dev-kit Mainverified | Aug 15, 2026 | 11 | |
| hi-predict Five expert personas independently analyze proposed changes before implementation to catch architectural, security, performance, and UX issues early. Uses mind_mcp for project context and graph_mcp for code impact analysis. Produces GO/CAUTION/STOP verdict with consensus agreements, conflict resolutions, and risk mitigations. Use before major features, refactors, or risky changes. baka3k/dev-kit Mainverified | Aug 22, 2026 | 2 | |
| 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-reverse Reverse Engineering C and C++ modules into validated use-case, module, and C++-to-Java migration artifact packages. Generates evidence-backed traces, sequence/class/state/activity/architecture diagrams, entry-point/interface/data/business-rule/error/concurrency catalogs, parity mappings, risks, tests, reviews, and coverage; exhaust mind_mcp and graph_mcp before Serena, and use native source tools only as a final fallback. baka3k/dev-kit Mainverified | Aug 22, 2026 | 57 |
Plan implementations, design architectures, create technical roadmaps with detailed phases.
source snapshot Aug 22, 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
Synthesize existing module-inventory and tech-audit artifacts into an architecture summary, per-module breakdown, risk assessment, and optional Mermaid diagrams. Do not inspect source from scratch or run full onboarding.
source snapshot Aug 15, 2026
Create, edit, and visually validate client-ready PowerPoint presentations (.pptx) using a sanitized navy-white-orange-teal design system, with evidence-led storylines, natural executive copy, editable architecture/process/timeline/option layouts, and professional native charts derived from supplied CSV, JSON, spreadsheet, or tabular data. Use for executive proposals, consulting decks, technical architecture, current-state assessments, phased roadmaps, investment options, KPI reviews, and Japanese-customer-facing presentations where visual consistency, quantitative accuracy, privacy, and presentation readiness matter.
source snapshot Aug 15, 2026
Five expert personas independently analyze proposed changes before implementation to catch architectural, security, performance, and UX issues early. Uses mind_mcp for project context and graph_mcp for code impact analysis. Produces GO/CAUTION/STOP verdict with consensus agreements, conflict resolutions, and risk mitigations. Use before major features, refactors, or risky changes.
source snapshot Aug 22, 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
Reverse Engineering C and C++ modules into validated use-case, module, and C++-to-Java migration artifact packages. Generates evidence-backed traces, sequence/class/state/activity/architecture diagrams, entry-point/interface/data/business-rule/error/concurrency catalogs, parity mappings, risks, tests, reviews, and coverage; exhaust mind_mcp and graph_mcp before Serena, and use native source tools only as a final fallback.
source snapshot Aug 22, 2026