The lifecycle commands

These commands arrive with your workspace's organ pack, not with the application. The Cockpit cheatsheet describes the standard lifecycle surface. Your installed organ-pack version and the `/ws-` command picker determine which commands are actually available in a particular workspace.

The commands are more than shortcuts. Together they carry intent, design, implementation, tests, reviews, release evidence, and learning through one governed lifecycle. SOCK grounding gives the agent a bounded view of the existing estate; the organ pack supplies the method; SOCM receives the work and gate evidence. Use the cheatsheet to discover what your workspace currently supports, then open an individual command for its exact inputs and checks.

Stage 1 · Ideation

CommandWhat it does
/ws-ideateStart ideation for a new capability — interactive PRD and HLD capture, creates the Jira epic, syncs to Command Center

Stage 2 · Inception

CommandWhat it does
/ws-decomposeDecompose an approved epic into stories with acceptance criteria
/ws-designCreate the architecture design (LLD) with options analysis and a security gate

Stage 3 · Construction

CommandWhat it does
/ws-startStart work on a story — pulls ancestor artefacts, creates the workspace, registers in Command Center, detects conflicts
/ws-clarifyLock requirements and define acceptance criteria from a question-and-answer round
/ws-assessAssess risk level, which sets the coverage and gate thresholds later commands enforce
/ws-planCreate a detailed, phased implementation plan from the approved design
/ws-implementMake focused code changes aligned to the plan
/ws-testgenGenerate unit and integration tests from acceptance criteria and the implementation
/ws-qualifyRun quality gates — lint, types, tests, coverage, security, build — to qualify code for review
/ws-reviewComprehensive code review, standalone or self-review
/ws-diagnoseDiagnose a bug — build a reproduction, write a failing test, confirm it fails before fixing
/ws-security-reviewIndependent security review for security-sensitive changes

Stage 4 · Validation

CommandWhat it does
/ws-shipCreate the merge request with evidence, merge to the QA line, deploy to QA, notify QA
/ws-certifyQA independently tests the deployed feature and produces the Gate 4 certification evidence

Stage 5 · Operation

CommandWhat it does
/ws-learnCapture learnings and fold them back into rules, checklists, and templates
/ws-completeComplete a task — final sync, archive the workspace, mark the manifest completed

Cross-stage utilities

CommandWhat it does
/ws-askUniversal entry point — answer questions, brainstorm, evaluate architectures, trace impacts
/ws-statusShow workflow status and resume or restart from any step
/ws-switchSwitch between tasks, saving the current context
/ws-cancelCancel an accidental task initiation within the grace period
/ws-doctorHealth check — connectivity, authentication, and workspace state. Read-only
/ws-approveReview and approve an artefact contribution — the consensus step before implementation
/ws-syncPush local artefacts to Command Center, or pull remote ones

Controlled add-on commands

The shipped framework also contains the following commands for controlled add-on authoring and workspace installation. They are not currently listed in Cockpit's built-in command cheatsheet.

CommandWhat it does
/ws-addon-listList add-ons installed in the current workspace, including their versions and registered content
/ws-addon-installPreview and transactionally install a packaged add-on into the current workspace; collisions are refused rather than overwritten
/ws-addon-uninstallRemove the files registered to an installed add-on, with drift checks that protect locally modified content
/ws-addon-validateValidate an add-on directory or package against the MSOCK Add-On Standard
/ws-addon-packageValidate and package an add-on into the canonical distributable archive
/ws-addon-reserveTemporarily reserve an add-on prefix before its first publication
/ws-addon-publishValidate and submit a packaged add-on to the portal's controlled review workflow
/ws-addon-promoteRequest platform-wide distribution for an enterprise-owned add-on that has already been published

Maintainer commands

CommandWhat it does
/ws-knowledge-captureCapture and update platform knowledge for the workspace
/ws-triageWork the maintainer queue of contributions, friction reports, and staleness alerts
/ws-distribute-sockPublish a versioned knowledge bundle for a workspace
/ws-distribute-sociPublish a versioned organ pack for a workspace
/sock-compareCompare two SOCK harnesses and show what changed between them
/fit-gapCompare the current estate with a target state to identify gaps

/sock-compare and /fit-gap are reference entries shown in the current Cockpit cheatsheet. They are not command files in the base organ pack reviewed for this documentation, so confirm that the target workspace's installed distribution provides them before relying on either command.

The two standard flows

Feature work

text
ideate → decompose → start → clarify → assess → design → plan →
implement → testgen → qualify → review → ship → certify → learn → complete

Bug work

text
start → clarify → plan → diagnose → implement → testgen →
qualify → review → ship → certify → learn

Gates the commands feed

GateChaired bySigned byEvidence
Gate 1 — IdeationProductProduct + Guild + Capability LeadPRD and HLD
Gate 2 — InceptionGuildGuild + Capability Lead, Product optionallyLLD and decomposition
Gate 3 — ConstructionReviewing engineerTech Lead peer, Security if flaggedCode review, security review, coverage, merge-request approval
Gate 4 — ReleaseCapability LeadCapability Lead + ProductQA certification

See gates, Jira and limits for how gates are decided in SOCM Command Center.

Models and effort

ModelThinking effortNotes
SonnetSupportedThe default model
OpusSupportedFor heavier reasoning
HaikuNot supportedFastest; the effort control is hidden

Effort levels are Low, Medium, High, X-High, Max, defaulting to High. Effort can be changed before a session starts and while one is running.

Integrations

IntegrationPurpose
JiraRead and write the epics and stories lifecycle commands refer to
GitLabRead and write merge requests and review evidence

Availability controls

Admin Console entryStatusEffect
AIDLC CockpitGenerally availableThe SOCI Cockpit tile and desktop experience
Cockpit Converged ChatLimited availability, off by defaultThe redesigned chat experience
SOCK AssistantGenerally availableThe in-product SOCK assistant

Current limits

  • Desktop only.
  • Claude Code is the only shipped agent runtime; Codex is disabled and does not appear.
  • Terminal scrollback is bounded and is not a permanent log.
  • Workspace files previewed in Cockpit carry no comments or shared review state.
  • Lifecycle commands depend on the workspace organ pack being installed; a workspace still being set up will not have them.