Map existing codebases to infer architecture, stack, conventions, and concerns.
npx skills add https://github.com/Qualiasolutions/qualia-framework --skill qualia-map
Please help me install this Agent Skill. Skill: qualia-map Source: https://github.com/Qualiasolutions/qualia-framework/tree/main/skills/qualia-map Command: npx skills add https://github.com/Qualiasolutions/qualia-framework --skill qualia-map
Mapping an unfamiliar or brownfield codebase is time-consuming and error-prone; this skill automates discovery to infer architecture, technology stack, conventions, and notable concerns so teams can onboard, plan, and prioritize work confidently.
Run the qualia-map skill in the project directory to produce a .planning/codebase README and four dimension files describing architecture, stack, conventions, and concerns.
High-intent search queries and answers about installing and using this skill.
To map an unfamiliar codebase, you can run an automated analyzer to infer architecture, technology stack, coding conventions, and notable concerns. This generates four structured markdown files and a synthesized README for onboarding.
Analyzing a brownfield repository before feature planning is best done by scanning the existing codebase to document architecture and stack details. This produces mapping artifacts that help you prioritize work and seed validated requirements confidently.
Yes, you can audit a client's source code without modifying it by using a non-destructive mapping tool. It reads the repository only, documents validated capabilities and issues, and optionally commits the generated mapping artifacts.
Documenting a tech stack and coding conventions for downstream automation involves generating machine-readable mapping artifacts. Four parallel analyzers create structured files for architecture, stack, conventions, and concerns.
Yes, codebase mapping works effectively for onboarding to existing projects by producing a single-page summary README. This synthesized file links to detailed dimension files, enabling new team members to quickly understand validated capabilities.
Mapping a codebase's architecture and concerns generates four structured files: architecture.md, stack.md, conventions.md, and concerns.md. These are synthesized into a single .planning/codebase/README.md for programmatic consumption.
MarkusonGenerate or update an index.md file with categorized file and subdirectory listings.
mol4Break product requirements into validated epics and user stories.
trymiraiValidates inference outputs by comparing them with reference results via Rust cargo test harness.
Pear-CommerceGenerate seven structured .planning/codebase/ documents via parallel mapper agents.
