Skip to content

feat: add multi-destination planning with start-planning command#8

Merged
leeovery merged 4 commits intomainfrom
claude/planning-implementation-handoff-014Lpha3AU2KTr96yGndeiMC
Dec 9, 2025
Merged

feat: add multi-destination planning with start-planning command#8
leeovery merged 4 commits intomainfrom
claude/planning-implementation-handoff-014Lpha3AU2KTr96yGndeiMC

Conversation

@leeovery
Copy link
Copy Markdown
Owner

@leeovery leeovery commented Dec 8, 2025

Add support for storing plans in different formats:

  • Local markdown (single plan.md file)
  • Linear (via MCP with local pointer file)
  • Tasks.md (directory structure for Kanban UI)

Changes:

  • Create output adapter reference files for each destination
  • Add start-planning command to discover discussions and route to destinations
  • Update implementation skill to read plans from any format
  • Update review skill to find plans in different locations

The planning skill approach remains the same regardless of destination.
Only the output format changes based on user choice.

Add support for storing plans in different formats:
- Local markdown (single plan.md file)
- Linear (via MCP with local pointer file)
- Tasks.md (directory structure for Kanban UI)

Changes:
- Create output adapter reference files for each destination
- Add start-planning command to discover discussions and route to destinations
- Update implementation skill to read plans from any format
- Update review skill to find plans in different locations

The planning skill approach remains the same regardless of destination.
Only the output format changes based on user choice.
All plan formats now use a single entry point: plan.md
The format field in frontmatter declares the source:
- format: local-markdown - full plan content inline
- format: linear - query Linear via MCP (includes project_id)
- format: tasks-md - read task files from subdirectories

This simplifies discovery (always check plan.md) and makes
the format self-describing rather than inferred from filename.
Backlog.md is a better fit for the workflow:
- Native MCP support for Claude Code
- Richer task metadata (priority, labels, dependencies)
- Git-native with auto-commit support
- Terminal and web Kanban views

Changes:
- Replace output-tasks-md.md with output-backlog-md.md
- Update all format references from tasks-md to backlog-md
- Update plan-sources.md with Backlog.md reading instructions
- Update start-planning command options
Remove duplicated format/structure details and reference the
planning skill's output adapters instead. Keep only
implementation-specific content:
- Detection table (quick reference)
- Reading/query steps
- Progress update instructions
- Fallback handling
- Execution workflow

Reduces maintenance burden - format details in one place only.
@leeovery leeovery merged commit 281a6cc into main Dec 9, 2025
@leeovery leeovery deleted the claude/planning-implementation-handoff-014Lpha3AU2KTr96yGndeiMC branch December 9, 2025 14:59
leeovery added a commit that referenced this pull request Apr 20, 2026
…ng changes

report_update was called unconditionally after the node block, even
when zero manifests were modified. The orchestrator's counter (and the
'review changes' prompt it gates) now fires only on real updates. The
node pass exits 2 on no-op; the bash wrapper routes that to
report_skip instead.

Also made the rc capture robust under the orchestrator's 'set -eo
pipefail' — previously a non-zero node exit aborted the orchestrator
at the rc=$? line.

Closes deferred-issues #8.
leeovery added a commit that referenced this pull request Apr 20, 2026
…oc-only

Closes the deferred-issues ledger for the knowledge-base pre-merge
cleanup pass. 16 of 18 items fixed in code across earlier commits on
this branch; #7 ('--work-unit' as boost not filter) stays open as a
deliberate design choice already documented in SKILL.md.
leeovery added a commit that referenced this pull request Apr 20, 2026
…ferred #8

withRetry now bails on RangeError alongside TypeError/ReferenceError/
SyntaxError. Bad Math.min args, invalid array sizes, and similar
programming errors shouldn't burn 7s of retry budget.

Also withdraws deferred-issues #8 (migration 036/035 counter). Fixing
migrations retroactively only helps users who haven't yet run them —
the migration id is recorded in .workflows/.state/migrations after
first run and never re-executed. Snapshot principle > one-time
counter-reporting accuracy.
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.

2 participants