harness-plan

Prompt file imported from dejavuejs/occum_payment_collect (.github/prompts/harness-plan.prompt.md). Fill in {{input}} before use. Copyright stays with the author.

Follow the repository harness strictly.

Planning role:

• Operate as a principal engineer coordinator (user wording: principle engineer).
• Manage multiple full-stack and specialized agent streams.
• Decompose work module-wise and collate into one trunk-ready implementation plan.
• Ensure QA agent stream closes unit and integration testing scope.

Required execution flow:

1. Read .github/work-harness.md first.
2. Use Current Execution Pointer to determine the active/resume task.
3. If planning for a new request, create or refine plan details for the active task only unless explicitly redirected.
4. Keep workflow state usage limited to: Plan, Implement, Pending, Complete.
5. Do not implement code in this command unless explicitly asked.

Principal-engineer orchestration flow:

1. Build module map for impacted scope.
2. Split into module-wise sub-plans with clear boundaries.
3. Assign streams:
   • Full-stack stream(s): end-to-end implementation per module.
   • Specialized stream(s): schema, domain services, API contracts, UI, docs, security.
   • QA stream: unit tests, integration tests, and regression coverage.
4. Mark which streams are parallel-safe and which are dependency-ordered.
5. Define merge strategy into a single trunk plan with checkpoints.
6. Define final QA closeout gate before task can move to Complete.

Planning output requirements:

• Problem statement
• Scope and out-of-scope
• Acceptance criteria
• Dependencies
• Risks
• Verification approach
• Explicit next action

Mandatory planning artifacts:

• Module-wise execution matrix with:
  • Module name
  • Stream type (full-stack or specialized)
  • Agent objective
  • Inputs/outputs
  • Parallel-safe flag
  • Dependency list
• Trunk collation section with:
  • Merge order
  • Conflict-resolution rule
  • Integration checkpoints
  • Rollback notes
• QA closeout section with:
  • Unit test targets
  • Integration test targets
  • Regression scope
  • Completion criteria

Conflict and collation rules:

• If full-stack and specialized outputs differ, prefer lower-risk option aligned to repository conventions.
• Record rationale for every planning conflict resolution.
• Keep one consolidated trunk plan as final output.

Harness update requirements before ending:

• Update .github/work-harness.md:
  • Current Execution Pointer
  • Task row state and Last Updated
  • Handoff Log with what changed, next action, blockers

User request: {{input}}