request-devflow-plan

Entry point for the request-devflow-plan workflow — inspects the current repo and recommends the exact next command (plan, foundation, kickoff, audit, handoff), with a map of the full lifecycle. Use when the user invokes the plugin by name, asks how to use it, or wants to know where to start on a new or existing project.

Independent acceptance audit of a completed DevFlow plan — zero trust, re-measures every metric itself, audits without fixing. Produces a PASS / PASS WITH FINDINGS / FAIL report. Must run in a fresh session (no executor history) and only after all sprints claim completion.

Generate the DevFlow foundation for a repo without committing to a full plan — as-is docs/SPEC skeleton (architecture, contracts, glossary, decision log), the core Mermaid diagram set, a one-command verification gate runner, a codebase guide, and the diagram-led / SPEC-assisted workflow conventions. Use when the user wants just the documentation and diagram foundation, a SPEC skeleton, or architecture docs — no sprints, no execution plan. Triggers: foundation, bootstrap docs, SPEC skeleton, architecture diagrams, 基座, 地基, 文檔基座.

Generate a stakeholder-ready handoff document from a DevFlow plan's ledgers (PROGRESS, deviations, decisions, phase reports, final audit). First half in plain language for non-technical readers — changes and value, risks, decisions, approval points; second half a technical appendix.

Interactive orientation for the request-devflow-plan workflow — inspects the current repo (existing plan? documentation base? progress state?) and recommends the exact next command, with a map of the full lifecycle. Use when the user asks how to use request-devflow-plan, where to start, which command to run next, or wants a guided tour. Triggers: help, getting started, where do I start, 怎麼用, 怎麼開始, 教學, 入門.

Start or continue an execution session for a DevFlow plan. The span argument sets the scope — one sprint, a sprint range (batch), or a whole phase. Collects the maintainer's review sign-off interactively when the previous unit is unsigned; continue mode resumes from the ledgers, reconciles HEAD, and requires a green start.

Tech-lead interview (one question at a time, architecture and data-model forks first) that produces a complete multi-file DevFlow execution plan — iron rules, locked decisions, per-sprint commit tables, machine-verifiable acceptance, kickoff prompts, and a maintainer guide. Use when the user wants an execution or development plan for a new feature, large change, or multi-session refactor — including mid-plan amendments and remediation planning after a failed acceptance audit. Triggers: plan, 計畫, 制定計畫, 執行藍圖.