Shipping velocity
Source-grounded pack with Quality-Speed Tradeoff Check, Rework Root Cause Review, and Outcome Scope Slicer, plus 1 more.
Get this packGrounded in the complete Shipping velocity series.
Open the pack, choose a workflow, and follow its setup and input instructions. You can also open each workflow below.
10 source essays · 4 usable skills · reviewed Jul 2026
Use this pack when
Choose this pack when the work touches Shipping velocity and you need a bounded workflow with explicit inputs, a defined output, and human review gates.
Choose the job in front of you.
4 source-grounded skills. Load one workflow at a time.
Quality-Speed Tradeoff Check
Use this workflow when a team claims it must trade quality for shipping speed and needs risk-specific quality floors, small batches, staged rollout, observability, review, automated checks, rollback, and evidence to distinguish controlled learning from reckless full-blast exposure.
Output specification
Return a quality-speed release plan with quality_contract, failure_risk, quality_floor, staged_rollout, monitoring_gates, review_capacity, and release_disposition.
Rework Root Cause Review
Use this workflow when completed or in-progress product work must be redone and the team needs to trace rework to the timing and placement of uncertainty, decisions, specs, interfaces, reviews, feedback, dependencies, and quality detection rather than blaming effort or carelessness.
Output specification
Return a rework root-cause review with rework_event, knowledge_timeline, root_mechanism, system_conditions, earliest_detection, and repair_and_recurrence.
Outcome Scope Slicer
Use this workflow when a large feature, migration, rebuild, workflow, or deadline has too many dependencies and needs thin end-to-end user-outcome or learning slices with explicit constraints, fallback, quality boundary, deferred scope, and evidence for the next increment.
Output specification
Return an outcome scope plan with outcome_and_assumption, activity_backbone, slice_options, selected_slice, deferred_scope, and learning_sequence.
Shipping Delay Audit
Use this workflow when product teams work hard but ship slowly and need critical-path evidence about active versus waiting time, work in progress, queues, handoffs, decision latency, shared-resource constraints, platform friction, AI-driven constraint relocation, and reinforcing loops.
Output specification
Return a shipping delay audit with critical_paths, flow_and_wip, decision_latency, seam_findings, constraint, constraint_relocation, and intervention_and_recheck.
Keep consequential decisions explicit.
These workflows structure analysis and artifacts; they do not authorize autonomous external, personnel, financial, legal, security, or other high-impact action.