Skip to content
Skills Library
Management & product · Planning

casa-map

/casa-map

Show and approve the personalized company build map (levels, parallel tracks, and status). Use when the user asks to see the plan, the roadmap, the build map, or says casa map.

Repository
casa ↗
Licence
MIT
Last repository change
14.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Show and approve the personalized company build map (levels, parallel tracks, and status). Use when the user asks to see the plan, the roadmap, the build map, or says casa map.

Original author description

Show and approve the personalized company build map (levels, parallel tracks, and status). Use when the user asks to see the plan, the roadmap, the build map, or says casa map.

How it works

  1. Steps
  2. Rules
Original SKILL.md headings · 29 lines, 158 words
SKILL.md preview
---
name: casa-map
description: Show and approve the personalized company build map (levels, parallel tracks, and status). Use when the user asks to see the plan, the roadmap, the build map, or says casa map.
---

# casa-map

Renders the build map so the founder can see and approve the path.

## Steps

1. Read `company-brain/build-map.json`. If absent, tell the founder to run
   `casa-start`.

2. Render by level. For each selected level show its name, its status (locked,
   active, done), and within it the parallel tracks and their nodes with status
   (blocked, ready, in-progress, done, skipped). Mark the critical path and any
   human-gate nodes.

3. On request, explain why a playbook was selected or skipped (read its
   `selection_hint` and the profile), or why one waits on another (its
   `depends_on`).

4. Approval. If the map is newly created or revised, ask the founder to approve.
   On approval, mark the map committed in `ledger/`. On change requests, hand back
   to the planner for an incremental re-plan (diff only, preserve done work).

## Rules

- Read-only by default. Do not change status here; status changes flow through
  `casa-next` and the playbook runs.
- No em-dashes, no emojis.

Versions

The database has no other skills named casa-map.

Database snapshot: 13.11.2026 · package version 36e6a4bf8231 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90casa-strategy
    Create and maintain the company's durable strategy anchor: the target problem, the customer, the wedge and approach, the key metrics, and the current tracks of work. Written to company-brain/STRATEGY.md and read as grounding by every other casa skill. Use when starting, when…
  • 100casa-board
    Move several parts of the company forward at once. Casa picks a handful of independent pieces of ready work, aimed at the one problem holding the company back, drafts them in parallel, checks each against its quality bar, and commits only what passes. Use when you want a work…
  • 86bizopsmap-map
    Map how a business or a project works with the bizopsmap command, and render the map as one page. Use when asked to map a business, its operations, its hand-offs or its checks, or to bring an existing map up to date.
  • 90handoff
    This skill should be used when the user runs /rspec:handoff or asks to get the reverse spec ready to build, plan the build, or hand the spec to a coding agent. Gets the ADRs approved, picks the build engine (sdlc or Claude Code), writes <spec>/build-plan.md in dependency order…
  • 90agntcy-status
    Show AGNTCY/SLIM/CASA integration status — whether the optional SLIM runtime package is installed, whether a SLIM endpoint is configured, which transport is the default, and what the agntcy mod has seen this session. Use when the user asks "is AGNTCY configured?", "show…
  • 100product-planning-stinger
    Turn an approved strategy and UX package into a PRD map, saved wave plan, project Definition of Done and handoff packet. Use to plan the build order. Read README.md for the guide map.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.