Skill v1.0.2
currentAutomated scanMerge pull request #414 from gmickel/publish/qa-receipt-4.18.1
version: "1.0.2" name: flow-next-make-pr description: Render a briefing from the aid artifact and open or update a PR via gh. Auto-detects the spec from the branch. Supports --draft, --ready, --base, --memory, --dry-run, --update, and mode:autonomous. user-invocable: false allowed-tools: AskUserQuestion, Read, Bash, Grep, Glob, Write, Edit, Task
/flow-next:make-pr
The host authors one grounded aid object; flowctl validates, stores and renders the briefing. Read workflow.md, then its reached references. No extra model call or hand-assembled sections. Invocation authorizes push and PR creation; --dry-run previews without repository writes, push, PR edits or memory writes.
Read working-rules.md first; it holds for every step of this skill.
Define FLOWCTL from ${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl, then <plugin-root>/scripts/flowctl (two levels above this SKILL.md), then .flow/bin/flowctl, choosing the first executable. Never assume a global install. Parse $ARGUMENTS: the positional token is SPEC_ID; reject unknown flags and missing base values. Carry these values between tool calls:
| Argument | Variable / effect | ||
|---|---|---|---|
--draft, --ready | `DRAFT_FORCE=draft | ready; default auto`; last wins, note conflicts | |
--base <ref> or --base=<ref> | BASE_REF; default empty | ||
--memory | WRITE_MEMORY=1; default 0 | ||
--dry-run | DRY_RUN=1; default 0 | ||
--update | UPDATE_MODE=1; default 0; refresh an existing open PR | ||
mode:autonomous or FLOW_AUTONOMOUS=1 | AUTONOMOUS=1; default 0 |
Keep this skill inline so AskUserQuestion remains available. Ask only for missing information, with a recommended option; use a numbered prompt if the tool is unavailable. NEED_INPUT: means ask outside Bash and rerun with the answer. Autonomous gaps hard-error instead. PRs open ready unless --draft or open items (rules in create-and-finalize); a branch without a spec takes workflow.md's no-spec path. Never merge here. Evidence, paths and requirement attribution must be grounded in the export and receipts, with unknowns explicit rather than invented.