ship

Solid

This skill should be used when the user says 'ship', 'release', 'publish', 'ready?', 'what's left', or wants to know what remains before shipping. Gap analysis between current state and shippable.

AI & Automation 9 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
33
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

!`if [ -f .pyro/state.md ]; then cat .pyro/state.md; else echo "NO_PROJECT_STATE"; fi` !`if [ -f .pyro/contract.md ]; then head -80 .pyro/contract.md; else echo "NO_CONTRACT_STATE"; fi` !`if [ -f .pyro/surface.md ]; then head -40 .pyro/surface.md; else echo "NO_SURFACE_STATE"; fi` ## Persona Act as a pre-flight checklist co-pilot. You scan everything -- contracts, surface, codebase -- and present a clear picture of what's done, what's missing, and how long the gaps will take. You never judge incomplete work. You never pressure. You split everything into "ship-now" and "ship-later" so the developer always has a release path that doesn't require finishing everything. Your first output is always the complete checklist -- never a question. **Input**: $ARGUMENTS ## Interface ``` fn gather_evidence() // Load contract.md, surface.md, scan codebase for implemented vs planned fn build_checklist() // Categorize: done (verified), gap (missing/incomplete), nice-to-have (non-blocking) fn estimate_effort() // Per-gap effort estimate in hours fn propose_split() // Ship-now scope + ship-later backlog ``` ## Constraints Constraints { require { Load phase-map.md at runtime via @${CLAUDE_PLUGIN_ROOT}/skills/pyro/reference/phase-map.md and extract Gate G5 criteria as checklist backbone. G5 criteria (slice complete, acceptance tests pass, hardening complete) become top-level checklist sections. Overlay contract.md acceptance criteria on top of G5 sections. Each ...

Details

Author
pyros-projects
Repository
pyros-projects/limitless
Created
8 months ago
Last Updated
1 weeks ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

ship

Execute a predetermined spec. Ingests a finalized brief (docs/brief/<slug>/ with brief.md status ready + tasks.md) or an Accepted propose (PROPOSAL.md), locks a definition-of-done contract, implements it on the strongest available engine (agent-teams / subagents / solo, with ultracode awareness), keeps a tight leash with minimal risk-boundary checkpoints, and hands back a user-run verification bundle plus a trace ledger. For a bare prompt with no spec, ship derives a minimal inline execution contract then ships it. Triggers on "ship this", "ship the brief", "implement the brief", "execute the proposal", "build from tasks.md", "run the spec", "implement this". The universal implementer; it does NOT author the durable product/technical spec (that is brief and propose). Never runs build/test toolchain by default.

12 Updated today
mirkobozzetto
AI & Automation Listed

ship

Prepare, validate, and ship the current work. Issue number to close (optional): <argument> Use for /ship requests.

1 Updated 3 days ago
amurshak
AI & Automation Solid

ship

Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'. Add --verify to trigger an adversarial verifier wave on the diff before a human reads the PR.

52 Updated today
griffinwork40