真实业务场景

I am starting a new B2B dashboard from scratch. Help me set up Trellis for the first week of work.

First, ask for the missing product and tech-stack decisions. Then create a small first-task PRD and
the minimum specs needed for frontend structure, API shape, error handling, and tests.

trellis init -u alice

/trellis:start

"Create the first task for project foundation. Keep scope to auth shell, app layout, lint/typecheck/test commands, and one sample route."

This is an existing repo. Do not refactor code yet.

Inspect the codebase and propose a minimal Trellis bootstrap for the next feature task. Identify the
actual patterns used for API routes, auth checks, logging, tests, and frontend forms. Write specs only
for patterns supported by current code examples.

Create a Trellis task for team invitations.

The feature should let workspace admins invite users by email, resend pending invites, revoke invites,
and accept an invite. Include product requirements, out-of-scope items, data model changes, API shape,
frontend states, tests, and rollout risks.

# Team Invitations

## Goal

Workspace admins can invite teammates by email and manage pending invites.

## In scope

- Create invite
- Resend invite
- Revoke invite
- Accept invite
- Expiration handling

## Out of scope

- Bulk CSV import
- SSO provisioning
- Role templates

## Acceptance criteria

- Non-admin users cannot create, resend, or revoke invites.
- Expired invites show a recoverable error.
- Invite acceptance is idempotent.
- Tests cover permission checks and expired invite behavior.

Create a behavior-preserving refactor task for src/billing/invoice-service.ts.

First map current responsibilities, callers, side effects, and existing tests. Then propose the safest
sequence. Do not change behavior until we have characterization tests or clear existing coverage for
the important billing paths.

## Behavior that must not change

- Invoice totals must match existing calculation for active discounts.
- Failed payment attempts must still write audit logs.
- Email rendering output must remain byte-for-byte compatible for existing templates.
- Public API response shape must not change.

Plan a Trellis migration from direct fetch calls to the shared API client.

Find call-site patterns, group them by risk, choose a small pilot batch, define verification commands,
and create separate tasks for low-risk, medium-risk, and high-risk files. Do not migrate everything in
one PR.

Fix the duplicate checkout submission bug.

Reproduce the issue, identify the smallest safe patch, add a regression test, and then run a
break-loop analysis. If the root cause is a missing convention, propose a spec update.

/trellis:start

"Users can submit checkout twice when the network is slow. Reproduce it, fix it, and add a regression test."

让 Trellis 运行 break-loop 分析。

Review the last few PR comments and help me convert repeated engineering feedback into Trellis specs.

Only propose rules that are concrete, enforceable, and tied to actual review comments. For each rule,
show the target spec file and a good/bad example.

Split this work into parallel Trellis tasks.

Identify dependencies, files likely to conflict, suggested branch names, PRD summaries, and the order
in which the PRs should be reviewed. Only parallelize tasks that can be reviewed independently.

base_branch: main
worktree_dir: ../.trellis-worktrees
tasks:
  - id: billing-settings
    branch: feature/billing-settings
    prd: |
      Add billing settings UI using existing settings page patterns.
  - id: invoice-export
    branch: feature/invoice-export
    prd: |
      Add CSV export for invoices using the existing export service.
  - id: plan-limit-banner
    branch: feature/plan-limit-banner
    prd: |
      Add plan limit warnings to the dashboard without changing billing APIs.

Create a Trellis rollout plan for one pilot repo and one department.

Include pilot criteria, first specs, task workflow, review policy for spec changes, platform adapter
setup, success metrics, and risks. Keep the first rollout small enough to complete in two weeks.