enterprise-plan

name	enterprise-plan
description	Use when an approved enterprise design exists and the next step is to turn it into an exact implementation plan with file paths, task boundaries, and verification commands

Enterprise Plan

Implementation-planning wrapper for portable enterprise work.

Required Background

• writing-plans

Inputs And Outputs

• Input: docs/designs/YYYY-MM-DD-<slug>-tdd.md
• Output: docs/plans/YYYY-MM-DD-<slug>-plan.md

Required Behavior

1. Re-read the approved design, the current repo profile, and the current codebase state.
2. Use writing-plans to break work into exact, bounded tasks.
3. Call out dependencies between tasks explicitly.
4. Define senior-architect file/module boundaries before tasks: owner, SRP, directory rationale, public seam, and expected consumers for every new or modified file.
5. Map every changed runtime file to an E2E/source-to-consumer trace and edge-case proof target.
6. Mark which tasks are safe for isolated-task execution and which are tightly coupled.
7. Include exact verification commands and expected outcomes, including live DB tests for schema/query work and headless browser tests for UI/PDF/file workflows.
8. Define the repo gate matrix up front: local commands that mirror required CI, PR body gates, no-new-mock gates, DB ownership gates, live-proof registry checks, and branch/base assumptions.
9. Record the design and plan artifact paths in the current agent session before handing off.
10. Hand off to enterprise-contract before any source edits.

If the approved design already exists and the prompt is only asking for the next step, treat this as STAGE_ONLY plan entry even when the larger program is still FULL.

If the prompt explicitly states that the committed repo profile and repo-local overlay are already current, do not reopen discover work by default.

Extra Enterprise Requirements

• Every deliverable in the design must appear in the plan.
• Every plan must name the contract file that will become the build gate.
• If the task touches a high-risk domain, include the proof-scope target and governing docs in the plan header.
• Planning may consume most of the lane. Schema, file-boundary, SRP, DB, and E2E uncertainty must be resolved here, not left for build.
• The plan must include a File And Module Architecture section and an E2E Trace And Edge Cases section.
• The plan must include a Repo Gate Matrix section. If required merge blockers, CI mirrors, PR-body rules, live proof commands, or ownership gates are unknown, stop before build instead of discovering them from CI.

Use plan-overlay.md for the extra enterprise fields to add on top of the normal planning workflow.