7.1 KiB
name, description
| name | description |
|---|---|
| plan-ticket | Create a complete implementation plan for a HiveGrid ticket from AGENTS.md, its ticket doc, linked planning sources, live Plane context, and current git state. Use when a user provides a HiveGrid ticket ID or asks to analyze, scope, sequence, or plan a ticket without implementing it yet. |
Plan Ticket
Plan only. Do not edit code, ticket docs, Plane, or external systems. Stop after the plan and ask for approval before implementation.
1. Resolve the ticket
Require a ticket ID such as AK-P3. Then:
- Read
AGENTS.mdcompletely enough to apply the current rules relevant to the ticket. - Read
.planning/ticket-docs/README.mdand.planning/ticket-docs/<TICKET-ID>.mdcompletely. Stop if the ticket doc is missing. - Follow only the granular sources linked by the ticket doc. Give
.planning/ENTITY-MODEL.mdpriority whereAGENTS.mdrequires it. - Read the current branch, recent commits, and diff against
origin/mainto establish what is already implemented. - Pull the live Plane ticket, comments,
blocked-by, andblocksusing.planning/plane-sync/fetch_ticket.pyor the available Plane integration. If Plane is unavailable, continue from Git and the ticket doc but state that evidence gap. - Never infer completion from a status badge alone.
2. Audit dependencies with three sources
Check both dependency directions. For every blocker or consumer, compare:
- Plane state and all relevant comments.
- Git/code reality, including merged commits and implementation notes.
- The blocker and dependent ticket docs.
Decide whether the exact contract needed by this ticket exists. When sources
conflict, apply the precedence rules in AGENTS.md; otherwise expose the
conflict instead of inventing a resolution. For cross-cutting contracts,
schemas, shared services, or blocks consumers, include the dependent
verification work in the plan.
3. Decide the delivery strategy
Classify every open item as:
selbst machbarextern/blockiertbewusst v2/out-of-scope
Recommend jetzt bauen, teilweise bauen, or zurückstellen, with a reason.
Do not pull work forward from later tickets.
For UI-heavy work, read .planning/INTERIM-UI-PLAYBOOK.md and
.planning/INTERIM-UI-DESIGN-STANDARDS.md. Missing final design does not
automatically block the ticket: plan the AD-28 interim screen when the ticket
permits it, and track final visual work as design-nachzug. Use finished
Automation/Forms screens and existing Settings Subscription/Billing interim
screens as style references.
If the ticket specifically integrates new or changed Subframe pages, also use
$subframe-einbinden and incorporate its inventory and integration
requirements.
4. Produce the plan in this order
- Plain-language introduction
- Current state and DoD percentage
- Dependencies and delivery strategy
- DoD-to-slices mapping
- Ordered build plan by slice
- Verification gates before commit
- Open questions and risks
- Reminder for post-build ticket-doc + Plane updates
5. Map every DoD item
For every DoD item, state:
- Status: done, open, or blocked.
- Fertigkeitskriterium: what must be true for full completion.
- Proof: the code path, test, screen, external artifact, or Plane evidence that proves it.
- Zählt NICHT als fertig: which partial implementation would be insufficient.
- Slice: where the work and verification happen.
Cross-check each DoD item against Was wir bauen, Benötigte Screens,
technical building blocks, Plane comments, and design notes. Count only fully
satisfied points. Report % = completed DoD points / total DoD points,
separating blocked work from work the developer can still do.
6. Make each slice executable
For each slice, name concrete files and include all applicable constraints:
- Loader/action builds the view model; UI receives VMs and callbacks.
- No
@prisma/clientor~/dbinpackages/ui-app/**. - No direct
packages/ui-subframeimport from routes. - No
useLoaderDatainsidepackages/ui-app/**. - Reuse audit, activity, notifications, search, permissions, tenant scope, and
other cross-cutting services from
AGENTS.md. - Use i18n keys and the existing clear-text error/state patterns.
- For UI, include interim/final visual state, smoke, hot-swap, and visual-baseline work as required.
- For schema work, use a module schema, develop with
prisma db push, and plan the current pre-merge migration/parity gates fromdocs/AGENT-CHECKLIST.mdwithout guessing around AD-21 timing.
Call out central registries whenever a slice adds or changes their inputs:
- Tenant-scoped Prisma model: tenant model registry plus ordering/tests.
- Workspace package subpath export: explicit Vitest alias plus consumer suites.
- Feature key: entitlements feature, blueprint, plan, and key-list tests.
- Permission key: permission seed, defaults, scope display, and de/en strings.
- Sidebar/navigation ID: UI registry, sidebar tests, and UI inventory mapping.
- UI text: de/en translations and i18n gates.
- Prisma schema: migration parity and the RLS live migration-chain gate.
7. Define verification before commit and push
Derive exact commands from docs/AGENT-CHECKLIST.md, the affected workspaces,
and .gitea/workflows/ci.yml. Include:
- typecheck, lint, and targeted tests for every affected package
- existing consumer suites for shared files, not only new tests
- applicable
verify:*registry, i18n, RLS, migration, bundle, or Docker gates - seed idempotency and browser/staging proof when the ticket requires them
- the no-US-provider and architectural anti-pattern checks when relevant
Do not schedule external writes, pushes, Plane changes, or Done transitions without explicit authorization.
8. Include the post-build audit reminder
Before any completion report or Done-state recommendation, perform a Ticket-Abschluss-Audit:
- Re-read the ticket doc and current Plane comments.
- Compare code state against every DoD item, required screen, and technical building block.
- Separate remaining work into
selbst machbar,extern/blockiert, andbewusst v2. - Count percentage only from fully satisfied DoD points. Partial backend-only or UI-only work does not count as a full DoD point.
- If a design ticket such as
D-*is referenced, state whether its delta is integrated, replaced by a valid interim baseline, or still blocking. - Update the ticket doc with date, proof, DoD checkboxes, and percentage before any Plane completion action.
- Mirror the result to Plane only with the required identity check and explicit authorization; set Done only at 100% DoD.
- If an interim screen was created, offer the optional David handover described
in
.planning/INTERIM-HANDOVER-GUIDE.mdinstead of creating it silently.
End the response after the plan and ask whether it should be approved or adjusted.
Mandatory constraints
- Follow
AGENTS.mdstrictly. - Stay in ticket scope.
- Keep generated Subframe app chrome out of app screen components.
- Mark out-of-scope ideas explicitly as
💡 Vorschlag (außerhalb Ticket-Scope): .... - If a source is ambiguous, stop and ask instead of inventing.