Build-test-deploy engineering: CI wall clock, bottleneck forecast, staged rollout, rollback point, runbook.
Early AccessEvery agent is free to connect — no card, no checkout. Paid agents are coming.
Browse › Software Development › Launch Kit Builder
Positioning, messaging, FAQ, and a dated checklist — all from what actually shipped.
A preview derived from this agent’s definition — not a live run. Nothing runs and no key is sent until you connect. FindAgent runs it on the hosted connection.
Fetch the epic with its scope, so the kit can be checked against what was actually planned.
Reaches: {jira_site}.atlassian.net
Uses your Atlassian Cloud token.
List what actually landed under the epic, to separate shipped from descoped.
Reaches: {jira_site}.atlassian.net
Uses your Atlassian Cloud token.
Fetch the spec or PRD the feature was built from.
Reaches: {confluence_site}.atlassian.net
Uses your Atlassian Cloud token.
Find previous launch kits, to stay consistent with how launches are done here.
Reaches: {confluence_site}.atlassian.net
Uses your Atlassian Cloud token.
Create one section of the launch kit as a Confluence page.
Reaches: {confluence_site}.atlassian.net
Uses your Atlassian Cloud token.
Create one dated launch checklist task. Never assigns a person you were not told owns it.
Reaches: {jira_site}.atlassian.net
Uses your Atlassian Cloud token.
Only ever sent to: atlassian.net
Format: Paste the Base64 encoding of “id:token” (e.g. your email and API token joined by a colon), not the raw token. Many tools show this ready-made as your “Basic auth” value.
This MCP server runs on your own machine — FindAgent only points you at it. Run the command below, then add it to your MCP client. Nothing is hosted or proxied on our side.
npx -y @findagent/mcp runPaste this into your client config (e.g. claude_desktop_config.json or a Cursor mcp.json), then restart the client.
{
"mcpServers": {
"launch-kit-builder": {
"command": "npx",
"args": [
"-y",
"@findagent/mcp",
"run"
]
}
}
}This agent will ask you for the following. You enter them when you connect — they're encrypted and never shared with the creator.
Base64 of 'your-email:your-api-token' — encode it yourself before pasting; the runtime only adds the Basic prefix. Create the token at id.atlassian.com/manage-profile/security/api-tokens. One credential covers Confluence and Jira on the same site. Needs page create and issue create.
Get this from atlassian.net's account or API settings.
Paste the value as a single line.
Only sent to: atlassian.net
Build-test-deploy engineering: CI wall clock, bottleneck forecast, staged rollout, rollback point, runbook.
Whose failure is this, and do these tests catch anything, from the CI, coverage and mutation evidence you paste.
Keeps asking until a request is genuinely buildable, then writes the use case, criteria and ticket drafts.
Turns an approved design into a typed component with its story, test, API contract and client SDK.
Maps your module graph, scores blast radius, plans migrations and composes a validated unified diff.
Decides whether a change can merge: diff review, test evidence, breaking-change and tech-debt scoring.
Sprint health, backlog hygiene, and an exec brief — from one Jira read, without managing anyone.
Manage Heroku apps, dynos, add-ons, Postgres, and pipelines.
Search Shopify's developer docs and validate your GraphQL and theme code.