Skill v1.0.0
currentAutomated scan100/100name: analisis-sistema description: "Trigger: analisis de sistema, educcion, ilacion, seudocodigo, EDU-, ILA-, SEU-, requisitos por ingenieria inversa. Documenta leyendo el codigo, sin inventar." license: Apache-2.0 metadata: author: "axioma (fork de gentle-ai)" version: "1.0"
Análisis de Sistema — Requisitos por ingeniería inversa
Activation Contract
Use when the user asks to document what an existing system already does: reverse-engineered requirements, educciones/ilaciones/seudocódigo, specs derived from code, or a docs/analisis-sistema/ tree. The failure mode this skill exists to prevent: writing plausible requirements documentation that no line of code actually backs.
This is NOT classical requirements elicitation gathered from interviews before building. It is reverse engineering: read the real code (schema and migrations, RPCs, authorization policies, frontend components, routes) and document what the system ALREADY does. Every "el sistema debe..." means "el sistema YA hace esto, según el código citado".
Artifacts are written in Spanish; this skill file and reasoning stay in English.
Hard Rules
- The ONLY source is the code. Never invent interview minutes, stakeholder quotes, or "el área confirmó...". The source catalog has exactly one real entry: FUE-0001, the project's source code.
- Never guess a function, column, table, endpoint, or migration name. Open the real file and cite its path. A name you did not read is a fabrication, even when it is the obvious name.
- Genuine ambiguity — something the code cannot settle — goes under "Decisiones a definir". It is never resolved by inventing an answer.
- Real inconsistencies found while reading (divergent names, dead code, missing validation, contradictory rules) are documented explicitly. Never hidden, never softened.
- Never restate a documented module's detail from a module that consumes it. Reference it by code ("ver EDU-0004").
- The number of ilaciones per module is whatever the code's real distinct flows demand. Never pad to a fixed count, never collapse two real flows into one.
- Confirm at least one concrete finding per module by grep before marking it done. "It looked right" is not verification.
- Propose the full module list and WAIT for the user's confirmation before writing any file. Correcting the module list after redaction is the single most expensive mistake in this workflow.
- The header templates are exact. Do not omit, rename, or reorder rows.
axioma analisis statusfails the module otherwise. - Mockups live in
docs/mockups/, imported withaxioma analisis mockup import, and referenced from their educción's "Mockups asociados". Never paste binaries elsewhere in the tree.
Process
- Explore the real project structure: routes, database schema, domains, modules. Read, don't assume.
- Propose the module list (EDU-0001, EDU-0002, ...) as a table, and stop. Wait for confirmation.
- Scaffold each confirmed module:
axioma analisis modulo EDU-00XX --nombre "<módulo>". - Redact each module from the real code: the educción, one ilación per real distinct flow, and one seudocódigo per ilación. Cite file paths for every rule.
- Verify with grep — at least one concrete claim per module — then run
axioma analisis status. A module iscompletoonly when the tool says so. - Report per module: files created, and every real finding (inconsistency, gap, dead code) encountered.
Decision Gates
| Situation | Action | |
|---|---|---|
| The module list is not yet confirmed | Write nothing. Propose and wait. | |
| A name is needed and not yet read | Open the file. Cite the path. Never infer it. | |
| The code cannot settle a question | "Decisiones a definir" — never an invented answer | |
| A real inconsistency appears | Document it explicitly in the educción, and tell the user | |
| A module consumes another one | Reference by code; do not duplicate its detail | |
| A flow has a distinct error/alternative branch | It belongs in Postcondiciones, with the real message | |
analisis status reports the module as pendiente | It is not done. Fix what it names. | |
| The user supplies a mockup | analisis mockup import <archivo> --edu EDU-00XX, then link it from the educción |
Output Contract
Per module: the created file paths, the count of ilaciones and why the code demands exactly that many, at least one grep-confirmed finding, and any real inconsistency or gap found. At the end of a run: the analisis status table, and the list of modules still pendiente with what each one is missing.
Read references/plantillas.md for the exact header tables before writing any artifact.