1. Review the app behind the website
A marketing site does not reveal every onboarding, payment or permission condition. The flow skill inspects the source your agent can access and prepares a minimized report. It distinguishes code findings, missing backend/provider context and reported tests from proof of deployment or customer drop-off.
Use the included manifest example and validator. Preview and redact the report before uploading; never include secret values, customer lists or an entire repository. You can import the report through the dashboard if your agent cannot connect.
See the emails you already have
The current skill inventories existing automations alongside recommended additions. Review actual available copy, triggers, recipients, timing and source evidence. Already implemented means a connected code path was reported; live status remains separate. Templates, partial wiring and missing provider context stay visible. Existing messages are preserved, and unresolved overlaps block additions.
Inventory review and JSON/Markdown export are available before purchase. If your existing emails cover everything, no generation or purchase is needed. Rescans show added, changed and not-seen findings without assuming an email was deleted.
2. Choose the coverage
Review recommended Include, Exclude and Already covered choices. A ten-step flow does not need ten emails. Existing verification, receipts and dunning remain owned by their existing systems. Unknown state blocks the affected intervention. Your agent can stage choices; human approval happens in the signed-in review page.
3. Approve the exact package
Generate original copy within your existing purchase and refinement limits. Review the saved revision and provider requirements, then approve an immutable package. Copy the handoff to your coding agent or download the package. The dashboard does not run commands in your repository. Changed source, coverage or plan requires renewed review.
4. Prepare and test in your application
The executable pilot targets a Node backend with Firestore, Cloud Tasks and Resend. Other providers can be identified but are not automatically supported. Reuse your existing infrastructure. The included runtime library needs your authoritative state resolver, sender configuration, queue identity, preference endpoint and tests; it is not an automatically deployed service.
Keep live sending disabled until you approve activation. Verify duplicate/reordered events, current completion, billing and role changes, suppression, unknown values, quiet hours and ambiguous retries. Agent-submitted implementation reports are labeled reported; they cannot mark an integration independently verified or approve sending.
MCP connection and permissions
https://sequenced.dev/api/mcpInitial discovery uses project:read discovery:write coverage:write for one owned product. Later generation uses plans:generate; paid package reads use reports:read with project context; reports use implementation:report. Only request the permissions needed for the task. The consent screen lists every requested permission. No grant authorizes customer repository execution, provider secrets or email sending.
Use get_project_context, submit_flow_snapshot, set_coverage_choices and get_review for discovery. Use request_plan, get_job_status, get_implementation_package and record_implementation_result for the later stages. There is no approval tool. The public client ID sequenced-inspector supports the documented loopback callback; compatible clients may register validated callbacks. Test your particular host; MCP support is not universal compatibility.
Existing saved-plan handoff
Existing reports:read-only grants remain read-only and expose list_projects, get_report and get_implementation_spec. They do not acquire new write permissions. Your existing Markdown/JSON plans and implementation skill remain available. Historical plan downloads can select a saved revision.
What Sequenced operates
Sequenced stores the reviewed planning context and approvals. Your app owns customer identity, current product state, sending infrastructure and activation. No customer campaign runs inside Sequenced.