harness-delivery-workflow

Enforces a spec-first delivery lifecycle with discovery questions, RFC, Excalidraw architecture, and ADR gates.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill harness-delivery-workflow-miyake-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-delivery-workflow
Source: https://github.com/miyake-san/sogo-agent-platform/tree/main/skills/core/harness-delivery-workflow
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill harness-delivery-workflow-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into implementation without clarifying requirements, comparing alternatives, or recording decisions, leading to rework and undocumented trade-offs. This Skill enforces a spec-first delivery lifecycle so every engineering, AI, FDE, Databricks, or content change begins with structured discovery and approved design artifacts. ## Core Features & Use Cases - Structured Discovery: Requires 5–10 concise discovery questions, then restates answers, assumptions, scope, non-goals, and success measures for approval. - Mandatory Design Artifacts: Produces a specification, an RFC comparing alternatives, an editable .excalidraw architecture diagram, and an ADR recording the approved decision before any implementation. - Gated Incremental Delivery: Breaks work into tracer-bullet increments with tests and evidence, blocking implementation until all five gates are approved. - Use Case: When asked to add a new Databricks pipeline, the Skill first gathers discovery answers, drafts the spec/RFC/ADR set, and only then permits coding with recorded test evidence. ## Quick Start Ask the agent to plan and deliver a new feature using the spec-first delivery workflow with discovery questions, RFC, architecture diagram, and ADR before implementation.

Frequently Asked Questions about harness-delivery-workflow

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

FAQPage Schema
How do I enforce a spec-first workflow before implementation?

Activate this workflow so the agent classifies intent and risk, asks 5–10 discovery questions, and produces a spec, RFC, Excalidraw architecture, and ADR. Implementation is blocked until all five gates are approved.

What artifacts does a spec-first delivery process require?

This workflow requires four linked artifacts: a specification, an RFC comparing viable alternatives, an editable .excalidraw architecture diagram with SVG/PNG projection, and an ADR recording the approved decision and revisit triggers.

How many discovery questions should be asked before starting a project?

The workflow mandates 5–10 concise discovery questions, preferably in one batch. Follow-up questions are allowed only when an answer creates material ambiguity about scope or approach.

Can hooks approve delivery gates automatically?

No. Hooks act as enforcement only: they may block premature implementation but must not invent decisions or approve gates. Approval always requires explicit human sign-off on the restated scope and artifacts.

When should I not use a full spec-first delivery workflow?

The process is heavyweight for trivial fixes or typo-level changes where discovery, RFC, and ADR overhead exceeds the risk. It is designed for engineering, AI, FDE, Databricks, or structured content changes with real design trade-offs.