Skip to content

feat: Investigation targets in task specs#11

Merged
z23cc merged 3 commits intomainfrom
fn-23-investigation-targets-in-task-specs
Apr 6, 2026
Merged

feat: Investigation targets in task specs#11
z23cc merged 3 commits intomainfrom
fn-23-investigation-targets-in-task-specs

Conversation

@z23cc
Copy link
Copy Markdown
Owner

@z23cc z23cc commented Apr 6, 2026

Summary

  • Add Phase 1.5 "Investigation" to flowctl phase registry and all phase sequences
  • Add --investigation CLI flag to flowctl task spec for patching ## Investigation targets sections
  • Update default task spec template to include empty investigation targets placeholder
  • Add Phase 1.5 to worker agent: reads Required files before coding, greps for similar code, skips gracefully when no targets
  • Update plan skill template with investigation targets (Required/Optional structure) and rules
  • Add good/bad examples to plan skill examples.md
  • Teach plan-sync to detect and update stale file paths in investigation targets sections

Test plan

  • cargo test --all — 293 passed
  • flowctl validate --epic — clean
  • Manual: create task with --investigation flag and verify section patching
  • Manual: worker reads investigation targets before implementing

🤖 Generated with Claude Code

z23cc and others added 3 commits April 6, 2026 12:21
Add Phase 1.5 "Investigation" to the phase registry between Re-anchor
and TDD/Implement. Add --investigation flag to `task spec` command for
patching `## Investigation targets` sections. Update default task spec
template to include empty investigation targets placeholder.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ets template

Add Phase 1.5 to worker.md between Re-anchor and TDD/Implement phases.
Worker reads Required investigation target files before coding, greps for
similar functionality, then proceeds. Skips gracefully when no targets.

Update plan skill task spec template with ## Investigation targets section
(Required/Optional structure). Add good/bad examples to examples.md.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Teach plan-sync to detect stale file paths in ## Investigation targets
sections of downstream task specs. When completed tasks rename/move
files, paths in Required/Optional targets are updated along with other
stale references.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@z23cc z23cc merged commit de49f78 into main Apr 6, 2026
1 check failed
z23cc added a commit that referenced this pull request Apr 9, 2026
P0 fixes (state loss — root cause of 5 issues):
- get_flow_dir() now walks up directory tree (FLOW_STATE_DIR env → walk-up → CWD)
  Fixes: #1 state loss, #3 state not persistent, #5 worker parallel fail,
  #9 .flow symlink issues. Same pattern as git finding .git.
- flowctl recover --epic <id> [--dry-run]: rebuilds task completion status
  from git log. Fixes #11 no recovery after state loss.

P1 fixes (guard + review):
- Guard graceful fallback: missing tools → "skipped" (not "failed").
  Only actual failures block pipeline. Fixes #8.
- Review-backend availability check: if rp-cli/codex not in PATH,
  auto-fallback to "none" with warning. Fixes #7.

P2 fixes (UX):
- Slug max length 40→20 chars. "Django+React platform with account
  management" → "fn-3-django-react-plat" not 40-char monster. Fixes #2 #12.
- Brainstorm auto-skip: trivial tasks (≤10 words, contains "fix"/"typo"/etc)
  skip brainstorm entirely. Fixes #6.
- --interactive flag: pause at key decisions. Fixes #10.

370 tests pass. Zero new dependencies.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant