CARBON — Engineering ConfidenceUser Guide
CHAPTER 50 / 60 Core + Pro

/carbon-map

Build or revisit a persistent product quality map with screenshot/widget inspection, paths and journeys, separate functional/business risks, adjustable weighting and ranked testing/regression-automation backlogs. Retain build changes and human steering; show explicit AI/human time and cost estimates for all test items.

Jay · Your AI test managerTesting operations

When to use it

You need to see journeys, risk and gaps spatially.

Before you start

Core shows the saved assessment map. Pro adds richer cross-build planning and retained priorities. Link map nodes to screenshots and evidence; unmapped areas are not covered by implication.

Try this in your coding agent.

/carbon-map Show the saved assessment map for checkout, including findings and evidence gaps.

Replace sample paths with your project. Slash names are shorthand; your host may use a plugin prefix or a skill picker. Invocation help →

ILLUSTRATIVE WALKTHROUGH

Checkout quality map

An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.

  1. 01Read context
  2. 02Analyze
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing checkout quality map. I’ll keep the scope and permissions explicit.

Analyze

Analyze: Show the saved assessment map for checkout, including findings and evidence gaps.

Show evidence

Here is the evidence trail to inspect: Cart → checkout → payment response → confirmation; timeout branch has no evidence link.

Report

The map makes an untested recovery branch visible. Only mapped scope is represented; no whole-app coverage claim.

CARBON

Example report

Illustration
Project → decisions → retained evidence
Project → decisions → retained evidence — TestBucks teaching screen

TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.

  1. TestBucks project
  2. Command action
  3. Reviewable output

Illustrated outcome

The map makes an untested recovery branch visible.

Evidence to inspect

Cart → checkout → payment response → confirmation; timeout branch has no evidence link.

Still untested / not established

Only mapped scope is represented; no whole-app coverage claim.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For checkout quality map, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Cart → checkout → payment response → confirmation; timeout branch has no evidence link. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

Only mapped scope is represented; no whole-app coverage claim.

The next decision

Decide whether the evidence calls for a focused check, a reviewed fix or more context. Do not convert a plausible example into a verified finding.

Adapt the example to your project

  1. Replace checkout quality map with a real feature, path or decision in your project.
  2. State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
  3. Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-map result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-test →/carbon-more →

Content checked against the local command definition: skills/carbon-map/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.