ship-new-subsystem-checklist

Community

A repeatable release checklist for Loom subsystems.

Authorz3z1ma
Version1.0.0
Installs0

System Documentation

What problem does it solve?

Shipping Loom subsystems requires coordinating core CLI, storage, docs, and UX tests to avoid late-stage defects and ensure a consistent release. This checklist provides a repeatable, guard-railed process to ship new subsystems with minimal risk.

Core Features & Use Cases

  • Public contract: Define the CLI shape, failure semantics, and a stable machine-readable mode.
  • Core implementation guidance: Place core behavior under src/agent_loom/<subsystem>/ with clear separation from I/O.
  • Storage and indexing: Decide on persistent artifact locations, indexing strategies, and durable state handling.
  • CLI wiring & UX: Create thin CLI entrypoints, standardized error messages, and smoke tests to prevent regressions.
  • Documentation & governance: Update subsystem README, git hygiene rules, and UX regression tests to ensure longevity.

Quick Start

Follow this checklist to ship a Loom subsystem.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: ship-new-subsystem-checklist
Download link: https://github.com/z3z1ma/agent-loom/archive/main.zip#ship-new-subsystem-checklist

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.