skills.rest
z3z1ma
z3z1maCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ship-new-subsystem-checklist

Coordinate CLI, storage, docs, and UX tests for releasing new core subsystems.

21|1|Updated Jan 31, 2026
Search Tags:#checklist#cli#quality#process#ship#subsystem#loom
One-click install
npx skills add https://github.com/z3z1ma/agent-loom --skill ship-new-subsystem-checklist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-new-subsystem-checklist
Source: https://github.com/z3z1ma/agent-loom/tree/main/.opencode/skills/ship-new-subsystem-checklist
Command: npx skills add https://github.com/z3z1ma/agent-loom --skill ship-new-subsystem-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about ship-new-subsystem-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is required to release a new Loom subsystem across development, staging, and production?▼

To ship a Loom subsystem, you must complete a release checklist covering CLI contract definition, core implementation placement, storage indexing, CLI wiring, documentation updates, and UX regression tests.

How do I structure core implementation for a Loom subsystem to separate behavior from I/O?▼

Place core behavior for a Loom subsystem under src/agent_loom/<subsystem>/ with clear separation from I/O, ensuring thin CLI entrypoints handle standardized error messages and prevent late-stage defects.

Does shipping a Loom subsystem require a machine-readable CLI mode?▼

Yes, shipping a Loom subsystem requires defining the CLI shape, failure semantics, and a stable machine-readable mode to ensure consistent releases and prevent regressions across environments.

What documentation and governance steps are needed to ship a Loom subsystem?▼

Shipping a Loom subsystem requires updating the subsystem README, following git hygiene rules, and adding UX regression tests to ensure longevity and consistent release quality across development, staging, and production.

Can I use this checklist to release a Loom subsystem without persistent artifacts or storage indexing?▼

No, shipping a Loom subsystem requires deciding on persistent artifact locations, indexing strategies, and durable state handling to avoid late-stage defects and ensure a consistent release.

Why does my Loom subsystem release need UX regression tests and smoke tests?▼

UX regression tests and smoke tests are required when shipping a Loom subsystem to prevent regressions, verify standardized error messages, and guard-rail the release process across development, staging, and production.

Related Skills

Explore More Software Engineering Skills→
z3z1maz3z1ma
21

sync-distributed-opencode-plugin

Monitors plugin filesystem changes and triggers rebuilds of dependent modules.

Community
Intermediate
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

staging-validation-phase

Orchestrate staging validation with smoke tests, migration checks, and rollback testing.

Community
Advanced
cosmixcosmix
53

wiring-test

Generate YAML metadata verifying feature integration within Loom plans.

Community
Intermediate
tloncorptloncorp
4

tlon

Retrieve Urbit profiles, channels, messages, and ship data via tlon-run.

Official
Advanced