finops-align

/finops-align — step 3: Stakeholder & Planning Alignment

The Definition-of-Ready checklist and the lifecycle vocabulary live in the glassity-five-steps skill. The three-point checklist is repeated below.

Purpose

Convert a scored opportunity into owned, contextualized, executable work. Alignment has two sub-phases with two different audiences, and this command routes between them:

• Opportunity level (alignment_step_1), the FinOps leader. Produce the organization-wide execution plan, triage out assignments that do not apply, and approve — which synthesizes a per-service brief into every remaining assignment and advances them. Path A below.
• Assignment level (alignment_step_2), the service owner. Refine the per-service brief, name the single accountable owner, and advance to execution behind the Definition-of-Ready gate. Path B below.

This command mutates, through lifecycle-approve-plan (Path A) or lifecycle-accept-plan (Path B). Every mutation goes through the binary's two-phase confirmation.

Variables

Variable	Source	Default	Meaning
TARGET	first positional arg	required	The opportunity id (Path A) or the assignment id (Path B).
OWNER	--owner	ask	Path B only. The single accountable owner. Ask if it is not supplied — diffuse ownership is how work becomes an orphan ticket.
PERSONA	--persona	both	Path B only. Plan framing: cfo for a savings floor with confidence intervals, devops for headroom and rollback latency.

Tool surface

• CLI: glassity --output=json opp show <opp-id> for Path A's authoritative re-read. Path B's re-read is owned by lifecycle-accept-plan. Note that opp show resolves opportunity ids only — an assignment id needs opp show-assignment.
• Path A mutation: the lifecycle-approve-plan skill. It confirms the org plan at plans/<date>-<slug>-plan.md is committed, then runs opp approve two-phase.
• Path B mutation: the lifecycle-accept-plan skill. It locates plan/<date>-<slug>-<service>.md, registers the artifact, and transitions the assignment — two-phase each.
• Path A triage: glassity opp transition <assignment-id> --target-state archived drops accounts and services that need no work before approving.
• Helpers: git to commit a plan and read a file's commit sha, ls to locate plan files.
• Subagent (optional): delegate deep per-opportunity investigation to opportunity-triage through Task when the plan needs heavy reasoning.
• Binary check: run command -v glassity before the first CLI call. If it is missing, stop and tell the user to install it with brew install glassity/tap/glassity or from https://github.com/glassity/cli/releases. No account yet? Sign up at app.glassity.cloud.