LATTICECMDLAYER Get the skill

A planning skill by CMDLAYER 01 / 05

MAKE EVERY
MOVE MATTER.

Map independent plans that move in parallel—and show where their results change one another. Make dependencies, shared leverage, and the assumptions between them visible.

Install Lattice Explore the method
FIG. 01 — SHARED LEVERAGEILLUSTRATIVE MODEL / NOT A LIVE RUN
Three lanes, one destination Three independent workstreams—product, customer insight, and distribution—move in parallel. Product pilot usage signals feed the customer insight plan; case-study proof then feeds distribution partner evaluation. PARALLEL WORKSTREAMS / SHARED TARGETCOMPOUND OUTCOME 01 / PRODUCT02 / CUSTOMER INSIGHT03 / DISTRIBUTION PILOTUSAGE SIGNALNEXT VERSIONLISTENEVIDENCECASE STUDYLANDSCAPEPARTNER FITTEST EVIDENCEPROOF DEPENDENCIES CONNECT WORKSTREAMS; THEY DO NOT ERASE THEM
01 / PRODUCTPilot → observed usage signals

HANDOFF 01 ↓ Product usage signals feed customer interpretation.

02 / CUSTOMER INSIGHTContext review → classified evidence

HANDOFF 02 ↓ Permissioned case-study proof informs partner fit.

03 / DISTRIBUTIONPartner evaluation → candidate test
PLAN / INSPECT / ADAPT↗ A ROUTE IS A SET OF TESTABLE IDEAS
STRATEGY, MADE LEGIBLE.SCROLL TO TRACE THE ROUTE ↓
[ 00 ]

Plans can move in parallel.
Their shared leverage is where momentum compounds.

FIELD
NOTES
↘

02 / THE METHOD

FROM INTENT TO ROUTE / 3 MOVES

Run plans in parallel.
Connect their leverage.

Give each workstream its own objective and state. Then show where an output in one plan changes the options, dependencies, or next move in another.

01

Define workstreams

Break a goal into coherent plans with their own owners, activities, and intermediate state changes. They can advance independently.

PLAN APLAN B
02

Connect the states

Map where one plan's result changes another plan. Make shared inputs and points of leverage explicit, not implied by a task list.

OUTPUTNEW STATE
03

Probe the bridges

Ask what must hold for a result to travel across plans. Test assumptions, and keep alternatives visible when the link weakens.

IFTHEN?
↗

A plan is a hypothesis about change. Treat each bridge as something to inspect, not a guarantee that reality will cooperate.

03 / TRACE A ROUTE

FIXED ILLUSTRATION / NO LIVE ENGINE

Separate plans.
Shared leverage.

Each fixed illustration has independent workstreams with their own purpose and observable state. Select a handoff to inspect its mechanism, uncertainty, and counterfactual.

SELECT A CROSS-PLAN BRIDGE TO INSPECT FIXED EXAMPLES / NO ENGINE CALL

CASE FILE / FIXED EXAMPLEL—01 / PILOT
DESTINATIONEarn a credible next step for a product pilot.KNOWN / ASSUMED

Known: a bounded product pilot can be offered. Assumed: its usage signals can be interpreted and shared with permission.

! / OPEN QUESTION

Will observed usage be clear, relevant, and consented for a case study?

INDEPENDENT WORKSTREAMS / PROPOSED HANDOFF ILLUSTRATIVE / ASSUMPTION
  1. A
    PRODUCT PLAN — Run a bounded pilotPurpose: test one workflow. Action: instrument one observation window → State: usage events and friction points recorded.
    WORKSTREAM 1
  2. B
    CUSTOMER INSIGHT — Interpret the signalsPurpose: understand use in context. Action: review usage with participant input → State: evidence is classified by relevance and confidence.
    WORKSTREAM 2
  3. ↗
    Bridge: customer evidence → case-study proofMechanism: relevant, permissioned evidence becomes a reviewable story. Uncertainty: are the signals clear, attributable, and shareable?
    CAUSAL LINK
  4. C
    PROOF ASSET — Validate a case studyPurpose: make the evidence legible. Action: verify claims and permission → State: a reviewable case-study draft.
    WORKSTREAM 3
  5. D
    DISTRIBUTION — Evaluate partner fitPurpose: assess a route to reach. Action: compare audience and claim fit → State: a candidate low-risk partner test.
    WORKSTREAM 4
Hypothetical: this proposed bridge is an assumption.
IF IT HOLDS

Illustrative possibility: a permissioned, verified story gives partner evaluation a concrete claim to assess.

NOTE / The routes and outcomes shown here are authored examples. They illustrate a planning lens; they are not generated by a live Lattice run.

04 / WHAT CHANGES THE PLAN?

When a bridge
doesn’t hold.

Plans get more useful when a weak link changes what you do next. Lattice makes room for the alternative route, not just the preferred one.

Bring the method to your workflow ↗
BRANCH TEST / EXAMPLE ONLYIF THE SIGNAL IS WEAK
WEAK USAGE SIGNALEarly pilot evidence
REFINE THE PILOTNarrow the workflow; observe again
REVISIT THE PREMISECheck whether the problem is real
ALTERNATIVES KEEP A PLAN HONEST↳ UPDATE THE ROUTE WITH WHAT YOU LEARN
SCOPE
CHECK
02A

A CLEAR BOUNDARY

Structure is not
proof.

Lattice is a host-authored planning skill. It can organize steps and help inspect coverage: dependencies, assumptions, causal links, alternatives, and stress tests.

The engine checks structure and coverage. It does not establish that a causal bridge is sufficient in the real world, validate evidence, or guarantee an outcome. The optional separate engine is not bundled here.

01 / ORGANIZEPlans & state changesMake the proposed route legible.
02 / SURFACEBridges & assumptionsName what the route relies on.
03 / CHECKStructure & coverageInspect completeness, not truth.
NO PROMISES ABOUT OUTCOMES ↘

05 / TAKE IT WITH YOU

REPOSITORY IN PREPARATION

Start with
the route.

The public repository is being prepared. The command and linked source paths will be ready once the repository is populated.

Repository ↗README ↗Example plans ↗
INSTALL / LATTICECMDLAYER
$npx skills add https://github.com/CMDLayer/Lattice --skill lattice

Copy the command to your clipboard when the repository is populated.

NO ACCOUNT REQUIRED TO INSPECT THE EXAMPLESMAKE THE NEXT MOVE COUNT ↗