skills.rest
victorp1leon
victorp1leonCOMMUNITY
Explore all skills by this author →
GitHub

phase3-intent-delivery

Orchestrate conversational intent delivery from specification to smoke-tested deployment.

Updated Mar 6, 2026
Search Tags:#handoff#spec-first#unit-tests#smoke-testing#runtime-wiring#intent-delivery
One-click install
npx skills add https://github.com/victorp1leon/openclaw-bakery --skill phase3-intent-delivery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phase3-intent-delivery
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/.codex/skills/phase3-intent-delivery
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill phase3-intent-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes and accelerates the end-to-end delivery of new conversational intents by enforcing a gate-driven workflow from specification to smoke-tested handoff.

Core Features & Use Cases

  • Spec-first workflow enforcement: ensures contracts and plans are in place before implementation.
  • End-to-end milestone gates: requires docs, runtime/tool wiring, unit tests, smoke coverage, and handoff closure.
  • Use Case: Applies to intents like shopping.list.generate, inventory.consume, schedule.* and similar.

Quick Start

Follow the phase-3 workflow to add a new intent by creating specifications, wiring runtimes and tools, adding tests, creating smoke coverage, and closing the handoff.

Frequently Asked Questions about phase3-intent-delivery

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

FAQPage Schema
How do I enforce a spec-first workflow for delivering new conversational intents?▼

Spec-first delivery requires creating specification documents and canonical contracts before implementation. This enforces deterministic workflows by gating runtime wiring, unit tests, and smoke scripts until contracts are approved.

What steps are required to take a conversational intent from specification to smoke-tested deployment?▼

End-to-end intent delivery requires passing milestone gates: creating spec docs, wiring runtimes and tools, adding unit tests, creating smoke coverage, and closing the handoff to meet definition of done criteria.

How does gated release work for conversational intents like shopping list generation or inventory consumption?▼

Gated release enforces deterministic milestone gates for intents like shopping.list.generate or inventory.consume. Intents must pass through spec docs, runtime wiring, unit tests, smoke scripts, and handoff closure before release.

Do I need to update canonical contracts and runtime wiring before adding unit tests for a new intent?▼

Yes, updating canonical contracts and runtime wiring is required before adding unit tests. The gate-driven workflow enforces a deterministic sequence where specifications and runtime wiring must be completed to meet definition of done criteria.

What is the best way to standardize handoff closure for new conversational intent delivery?▼

Standardizing handoff closure requires a gate-driven workflow enforcing collaboration artifacts, smoke test coverage, and definition of done criteria. This ensures deterministic delivery from specification to smoke-tested deployment.

When should I use a gate-driven workflow for intent delivery instead of direct implementation?▼

Use a gate-driven workflow for initiative work requiring deterministic delivery. It enforces milestone gates for spec docs, runtime wiring, unit tests, and smoke scripts, ensuring intents like schedule.* meet definition of done criteria before release.

Related Skills

Explore More Product & Management Skills→
ranvirsinghranvirsingh

speckit-plan

Generate design notes, data-model hints, API contracts, and ADRs for GitHub Issues.

Community
Advanced
jonathanmalkinjonathanmalkin
61

deploy-app

Automate web application deployment through staging and production environments.

Community
Advanced
danieldev24danieldev24

ci-cd-and-automation

Automates CI/CD pipeline setup and quality gates for code verification.

Community
Advanced
hidonguyenhidonguyen

ck:cook

Automate end-to-end software feature planning, implementation, testing, review, and finalization.

Community
Advanced