skills.rest
pi-ixel
pi-ixelCOMMUNITY
Explore all skills by this author →
GitHub

module-asis-analysis

Analyze module code to produce structured ASIS context evidence.

3|5|Updated Jun 22, 2026
Search Tags:#code analysis#software design#reverse engineering#module analysis#asis
One-click install
npx skills add https://github.com/pi-ixel/Awesome-Agent-Workflow --skill module-asis-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: module-asis-analysis
Source: https://github.com/pi-ixel/Awesome-Agent-Workflow/tree/main/skills/module-asis-analysis
Command: npx skills add https://github.com/pi-ixel/Awesome-Agent-Workflow --skill module-asis-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill performs ASIS (After the IS) analysis on module code, generating context evidence to support subsequent design and implementation decisions.

Core Features & Use Cases

  • ASIS Analysis: Reverse-engineer code to understand existing implementations and constraints.
  • Context Evidence Generation: Document evidence, assumptions, and findings in a structured format.
  • Use Case: When preparing for a TO-BE (To Be) design, use this Skill to analyze the AS-IS state of the codebase, identifying modules affected by a given requirement or change.

Quick Start

Run the module-asis-analysis skill to analyze the AS-IS state of the 'payment-audit' module for the 'AR07758-支持快速退款接口相关功能' requirement.

Frequently Asked Questions about module-asis-analysis

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

FAQPage Schema
How do I conduct ASIS analysis on module code to understand existing implementations?▼

Conduct ASIS analysis by reverse-engineering module code to identify components, relationships, and constraints, generating structured context evidence for subsequent design decisions.

What is ASIS analysis in software design and when do I need it?▼

ASIS analysis is an After the IS reverse-engineering process to document existing code implementations and constraints. You need it when preparing for a TO-BE design to analyze affected modules.

How do I generate context evidence for a specific requirement affecting a module?▼

Generate context evidence by running module-asis-analysis on the target module code, documenting findings, assumptions, and constraints related to the specified requirement in a structured format.

Does module-asis-analysis require specific architecture documentation to run?▼

Yes, module-asis-analysis requires access to source code and utilizes the .sdd/software_architecture.md file for defining module boundaries during the reverse engineering and context evidence generation process.

Can I use module-asis-analysis for reverse engineering code constraints and relationships?▼

Yes, you can use module-asis-analysis to reverse-engineer code, focusing specifically on identifying code components, their relationships, and constraints related to specified requirements.

What are the limitations of using ASIS analysis for module code changes?▼

ASIS analysis focuses solely on the existing AS-IS state of the codebase to support TO-BE design; it does not implement changes but rather generates structured context evidence for downstream decisions.

Related Skills

Explore More Software Engineering Skills→
ggazzoggazzo

reversa-archaeologist

Analyze legacy codebases module-by-module and extract algorithms, control flows, and data structures.

Community
Advanced
Rinzler78Rinzler78
1

bmad-agent-architect

Guide technical architecture decisions for scalable software systems and implementation planning.

Community
Advanced
pi-ixelpi-ixel
3

module-tobe-design

Generate module design specifications from ASIS evidence and requirements.

Community
Advanced
TonyQ-AITonyQ-AI
9

domain-modeling

Extract core business concepts, entity relationships, and domain rules from requirement specifications.

Community
Intermediate