greenfield-delivery

MCP connector

Server URL

https://mcp.atlassian.com/v1/mcp/authv2Copy

Login

OAuth

Skills

13 in the Claude listing

• Architecture designUse when producing the engagement design document, choosing architecture or stack for a client project, or generating the client repository's CLAUDE.md and AGENTS.md.
• Build loopUse when actually building - working a task from pick-up to merge with an agent, verifying the result, reviewing agent-written code and tests, and handling what to do when the build shows the specific
• Build standardsUse when writing code, tests, or reviews on a client engagement, or when deciding whether work meets the engagement's definition of done.
• Business test casesUse when turning approved requirements into business test cases a person can execute - writing them, reviewing them, tracking their results, and taking them into handoff acceptance.
• discoveryUse when scoping a new client engagement before requirements - running a discovery conversation, writing a problem statement, or producing an estimate range.
• Greenfield deliveryUse when working on a client greenfield engagement - starting one, moving through a delivery gate, writing requirements or design documents, syncing work to a tracker, or handing off.
• handoffUse when closing out a client engagement - assembling the delivery package, writing the runbook, or producing the engagement record for acceptance.
• Progress reportingUse when writing or updating a client-facing engagement status page for business stakeholders - in Confluence, ADO Wiki, or repository markdown.
• qeUse when automating test cases that already exist - generating Gherkin feature files from test-cases.md, deciding what should and should not be automated, wiring step definitions in the client reposit
• Requirements gateUse when writing or reviewing engagement requirements and acceptance criteria, or preparing the client sign-off that establishes the scope baseline.
• Tracker azure devopsUse when the engagement tracker is Azure DevOps and you need the ADO-specific mechanics - creating epics, features, or product backlog items, updating states, or writing ADO Wiki status pages.
• Tracker conventionsUse when deciding what belongs in a work item, ticket, story, or backlog item on a client engagement, and whether one is well-specified enough to assign to an agent.
• Tracker jiraUse when the engagement tracker is Jira and you need the Jira-specific mechanics - creating epics, stories, or issues, updating status, writing Confluence status pages, or assigning work to Claude Age