dev-flowlisted

Lightweight development flow — the default track for everyday work. source-only changes, dev/staging live applies, and zero-user production (owner-declared). Evidence is a merged PR + green CI + one ledger line; no sealing, no successor tickets, no verdict ping-pong. Routes irreversible or customer-visible work to prod-flow via a one-question track test. Keeps hollow-green defenses and a fix-plus-regression-gate rule for problems found live.
reoring/sds · ★ 2 · AI & Automation · score 75

Install: claude install-skill reoring/sds

# dev-flow — lightweight development flow (default track) **English** | [日本語](SKILL.ja.md) ## Principle (one line) **Concentrate rigor at irreversible mutation gates; everywhere else, ship fast and let CI + PR review + regression gates carry the discipline.** Ceremony that duplicates a runtime fail-closed check is paying for the same safety twice. This split was distilled from a real failure mode: a flow built for one-shot irreversible launches (sealed receipts, successor tickets, verdict documents) leaked into everyday development and made everything slow — while adding no safety where it was applied. ## The track question (ask first, every time) **"If this fails, do we lose a non-refundable consumable (approval, signature, publication, quota) — or does a real customer see it?"** - **No → this skill (lightweight, the default).** - **Yes → [prod-flow](../prod-flow/SKILL.md)** — the full staged flow with packet sealing and a human GO gate. Examples: - Lightweight: source-only changes (PR/CI cycle), live applies to dev/staging estates, production with zero real users (owner-declared — see below). - prod-flow: customer-visible production mutation, signing/publication semantics, org-level authority (account vending, permission changes), anything that consumes a one-shot tuple. Never carry prod-flow equipment (packets, sealing, successor tickets, write-ahead receipts) into the lightweight track. ## Lightweight rules - **No sealing, no receipt-SHA reporting, no