skills.rest
DuongMQuang
DuongMQuangCOMMUNITY
Explore all skills by this author →
GitHub

3-handoff

Generate ROADMAP.md from project documents with TDD and logging gates.

6|Updated Mar 9, 2026
Search Tags:#tdd#logging#verification#roadmap#handoff#gate
One-click install
npx skills add https://github.com/DuongMQuang/quangflow --skill 3-handoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 3-handoff
Source: https://github.com/DuongMQuang/quangflow/tree/main/plugins/quangflow/skills/3-handoff
Command: npx skills add https://github.com/DuongMQuang/quangflow --skill 3-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams through the Phase 3 handoff by generating ROADMAP.md, enforcing TDD/logging mandates, and applying the SHIP/REFINE gate to delivery.

Core Features & Use Cases

  • ROADMAP generation: produce milestone-level plans from REQUIREMENTS.md, DESIGN.md, and CONTEXT.md with clear phase deliverables.
  • Discipline enforcement: embed TDD, structured logging, and verification gates into every implementation phase.
  • Context-aware review: integrate GOTCHAs, plan-level decisions, and evidence storage for audit trails.

Quick Start

Run the Phase 3 handoff to generate ROADMAP.md and apply gated progress with TDD, logging, and verification artifacts.

Frequently Asked Questions about 3-handoff

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

FAQPage Schema
How do I generate a ROADMAP.md for project milestone handoffs?▼

Generate a ROADMAP.md by feeding REQUIREMENTS.md, DESIGN.md, and CONTEXT.md into the handoff orchestration process. This produces milestone-level plans with clear phase deliverables, embedding TDD, logging, and verification gate requirements directly into each implementation phase.

What is a SHIP/REFINE gate in roadmap-driven delivery?▼

A SHIP/REFINE gate is a verification checkpoint applied during roadmap delivery to enforce production-grade discipline. It evaluates whether a phase meets TDD, structured logging, and verification artifact requirements before allowing progression to the next milestone.

How do I enforce TDD and logging mandates across implementation phases?▼

Enforce TDD and logging mandates by embedding them directly into ROADMAP phases and their evidence directories. The handoff orchestration captures verification artifacts and guardrails for each phase, ensuring audit trails and production-grade discipline are maintained.

Can I use handoff orchestration without existing CONTEXT.md or DESIGN.md files?▼

Handoff orchestration relies on REQUIREMENTS.md, DESIGN.md, and CONTEXT.md to inform ROADMAP phases. Without these input files, the tool cannot generate context-aware milestone plans or integrate plan-level decisions and GOTCHAs into the delivery roadmap.

What's the best way to maintain evidence and audit trails during phase handoffs?▼

Maintain audit trails by storing evidence in dedicated directories within each ROADMAP phase. The orchestration integrates plan-level decisions, GOTCHAs, and verification artifacts, capturing structured guardrails throughout the milestone delivery process.

Related Skills

Explore More Product & Management Skills→
ByronWilliamsCPAByronWilliamsCPA
1

project-planning

Generate four planning documents from a project concept.

Official
Advanced
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
miles990miles990

verification-before-completion

Run verification commands and report results only when checks pass.

Community
Advanced
Sh3rd3nSh3rd3n
3

verify

Verify project phase deliverables against acceptance criteria and roadmap success metrics.

Community
Advanced