skills.rest
dikini
dikiniCOMMUNITY
Explore all skills by this author →
𝕏@dikiniGitHub

bk-analyze

Reverse engineer brownfield codebases into BK-compatible specifications.

Updated Mar 3, 2026
Search Tags:#code analysis#documentation#reverse engineering#legacy systems#specification generation#brownfield development
One-click install
npx skills add https://github.com/dikini/knot --skill bk-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bk-analyze
Source: https://github.com/dikini/knot/tree/main/.agents/skills/bk-analyze
Command: npx skills add https://github.com/dikini/knot --skill bk-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reverse engineering existing, undocumented codebases into formal specifications, bridging the gap between legacy systems and modern development workflows.

Core Features & Use Cases

  • Codebase Analysis: Scans and analyzes existing code to identify business rules, interfaces, and behaviors.
  • Specification Generation: Creates machine-readable specifications compatible with the BK development ecosystem.
  • Use Case: When inheriting a legacy system with no documentation, use this Skill to generate initial specifications for its authentication module, enabling further analysis and modernization.

Quick Start

Analyze the codebase located at /path/to/legacy/app and extract specifications for the 'user-auth' component.

Frequently Asked Questions about bk-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reverse engineer a legacy codebase to generate specifications?▼

To reverse engineer a legacy codebase, you need a local codebase path and a specific component name. The analysis scans existing implementations to extract business rules, interfaces, and behaviors, generating formal business-compatible specifications for incremental modernization and documentation.

Can I generate documentation for an undocumented brownfield system automatically?▼

You can generate documentation for a brownfield system by providing its codebase path and target component name. The process extracts business rules and behaviors directly from existing code, automating the creation of formal, machine-readable specifications.

What inputs do I need to extract business rules from existing code?▼

Extracting business rules from existing code requires the codebase path and the specific component name for analysis. You can also specify analysis depth and define particular entry points to target the extraction of interfaces and behaviors accurately.

Does this work for incremental modernization of legacy systems?▼

This approach works for incremental modernization by bridging the gap between legacy systems and modern workflows. It reverse engineers existing implementations into BK-compatible specs, enabling structured analysis and phased modernization of undocumented codebases.

What is the best way to analyze specific entry points in a legacy codebase?▼

The best way to analyze specific entry points is to provide the codebase path and component name, then use the available options to define depth and specific entry points. This targets the extraction of business rules and behaviors for specification generation.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

explain

Trace code paths with file:line references and ASCII diagrams.

Community
Advanced
zachbuttonzachbutton
2

pyrs-apply

Generate code from pyramid specifications using incremental test-driven development.

Community
Advanced
erikliebeneriklieben
7

meta-continuous-learning

Extract reusable patterns and rules from session history and decision logs.

Community
Advanced
fanguyunfanguyun

spec-miner

Extract specifications from codebases and output them in EARS format.

Community
Advanced