Mapear

Skill adriannoes/awesome-agentic-ai/cursor-claude-codex/skills/igoruehara-spec-driven/skills/mapear

329 agent skills (Cursor, Claude Code & Codex), 5,380 OpenClaw skills, 201 ML notebooks, 7 textbooks, 52 research papers, 17 industry reports for PMs, Designers & Developers.

Install

npx -y skills add adriannoes/awesome-agentic-ai --skill mapear

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Use to map an existing (brownfield) codebase and produce docs/architecture/assessment.md — stack, architecture, implicit bounded contexts, maturity across the 5 axes, debts/risks, and historical decisions to become retroactive ADRs. Re-running updates the assessment. It is called by /kickoff in brownfield mode, and also runs standalone when the codebase changes or to analyze a repo. Trigger with /mapear.

SKILL.md

2.4 KB, 458 tokens by cl100k_base, as published. Nobody here has run it

Translation note: Originally authored in Portuguese (pt-BR) by Igor Uehara (igoruehara/spec-driven, MIT). Translated to English by this hub to keep the repository language consistent. Original content unchanged in meaning; see the upstream repo for the pt-BR source.

Skill: Map the current state (as-is)

Produces a portrait of a project already in progress. First read the code, then ask only what the code does not reveal. It is idempotent: re-running updates docs/architecture/assessment.md.

Process

Automated mapping: identify stack, folder structure, architecture style, couplings, tests/CI, logs/metrics/tracing. Infer the implicit bounded contexts from the code organization. In large repos, delegate the scan to an exploration subagent (see docs/engineering/_templates/subagent.template.md) to keep the context lean.
External inputs (if any): if /integracoes connected GitHub/cloud/Confluence (validated account), use them to enrich the as-is. Cite the source.
Gap interview (AskUserQuestion): current business intent and North Star; biggest pains/risks today; domain terms that confuse the team; what MUST NOT break; team context and size.
Gap analysis: compare the as-is with the SDD standard across the 5 axes (tech stack, architecture, infrastructure, quality, observability). Mark risk (low/medium/high).
Historical decisions: list structural choices already made without a record → they become retroactive ADRs (status: accepted, recording the historical rationale).

Outputs

docs/architecture/assessment.md (use docs/architecture/_templates/assessment.template.md).
List of retroactive ADRs to create in docs/architecture/adr/.

Next step

Inside /kickoff: feed the assessment + gaps back into the 5 axes and the roadmap.
Standalone: suggest /roadmap (to prioritize the mapped debts) or /camada-agentica.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.