
flow-next-opencode-sync
by gmickel
OpenCode port of Flow-Next: plan-first workflows, Ralph autonomous mode (overnight coding with fresh context), multi-model review gates via Codex, re-anchoring to prevent drift, receipt-based gating.
SKILL.md
name: flow-next-opencode-sync description: Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
Manual Plan-Sync
Manually trigger plan-sync to update downstream task specs.
CRITICAL: flowctl is BUNDLED — NOT installed globally. Always use:
ROOT="$(git rev-parse --show-toplevel)"
OPENCODE_DIR="$ROOT/.opencode"
FLOWCTL="$OPENCODE_DIR/bin/flowctl"
Input
Arguments: $ARGUMENTS
Format: <id> [--dry-run]
<id>- task ID (fn-N.M) or epic ID (fn-N)--dry-run- show changes without writing
Workflow
Step 1: Parse Arguments
ROOT="$(git rev-parse --show-toplevel)"
OPENCODE_DIR="$ROOT/.opencode"
FLOWCTL="$OPENCODE_DIR/bin/flowctl"
Parse $ARGUMENTS for:
- First positional arg =
ID --dry-runflag =DRY_RUN(true/false)
Get cross-epic config (defaults to false):
CROSS_EPIC="$($FLOWCTL config get planSync.crossEpic --json 2>/dev/null | jq -r '.value // empty')"
if [[ -z "$CROSS_EPIC" || "$CROSS_EPIC" == "null" ]]; then
CROSS_EPIC="false"
fi
Validate ID format:
- Must start with
fn- - If no ID: "Usage: /flow-next:sync [--dry-run]"
- If invalid: "Invalid ID format. Use fn-N (epic) or fn-N.M (task)."
Detect ID type:
- Contains
.(e.g., fn-1.2) → task ID - No
.(e.g., fn-1) → epic ID
Step 2: Validate Environment
test -d .flow || { echo "No .flow/ found. Run flowctl init first."; exit 1; }
If .flow/ missing, output error and stop.
Step 3: Validate ID Exists
$FLOWCTL show <ID> --json
If fails:
- Task: "Task not found. Run
flowctl listto see available." - Epic: "Epic not found. Run
flowctl epicsto see available."
Stop on failure.
Step 4: Find Downstream Tasks
For task ID input:
# Extract epic from task ID
EPIC=$(echo "<task-id>" | sed 's/\.[0-9]*$//')
# Get all tasks in epic
$FLOWCTL tasks --epic "$EPIC" --json
Filter to status: todo or status: blocked. Exclude source task.
For epic ID input:
$FLOWCTL tasks --epic "<epic-id>" --json
-
Find source task (agent requires
COMPLETED_TASK_ID):- Prefer most recently updated task with
status: done - Else: most recently updated with
status: in_progress - Else: error "No completed or in-progress tasks to sync from."
- Prefer most recently updated task with
-
Filter remaining to
status: todoorstatus: blocked(downstream).
If no downstream tasks:
No downstream tasks to sync (all done or none exist).
Stop (success).
Step 5: Spawn Plan-Sync Agent
Build context and spawn via Task tool:
Sync task specs from <source> to downstream tasks.
COMPLETED_TASK_ID: <source task id>
FLOWCTL: $OPENCODE_DIR/bin/flowctl
EPIC_ID: <epic id>
DOWNSTREAM_TASK_IDS: <comma-separated list>
DRY_RUN: <true|false>
CROSS_EPIC: <true|false>
<if DRY_RUN>
DRY RUN MODE: Report changes but do NOT edit files.
</if>
Use Task tool with subagent_type: flow-next:plan-sync
Step 6: Report Results
Normal mode:
Plan-sync: <source> -> downstream tasks
Scanned: N tasks (<list>)
<agent summary>
Dry-run mode:
Plan-sync: <source> -> downstream tasks (DRY RUN)
<agent summary>
No files modified.
Error Messages
| Case | Message |
|---|---|
| No ID | "Usage: /flow-next:sync [--dry-run]" |
No .flow/ | "No .flow/ found. Run flowctl init first." |
| Invalid format | "Invalid ID format. Use fn-N (epic) or fn-N.M (task)." |
| Task not found | "Task not found. Run flowctl list to see available." |
| Epic not found | "Epic not found. Run flowctl epics to see available." |
| No source | "No completed or in-progress tasks to sync from." |
| No downstream | "No downstream tasks to sync (all done or none exist)." |
Rules
- Ignores config -
planSync.enabledis for auto-trigger; manual always runs - Any source status - source can be todo, in_progress, done, or blocked
- Includes blocked - downstream includes both
todoandblockedtasks - Reuses agent - spawns plan-sync agent, no duplication
スコア
総合スコア
リポジトリの品質指標に基づく評価
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
1ヶ月以内に更新
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
レビュー
レビュー機能は近日公開予定です

