Scout, plan, build with agile tracking
scout_plan_build_v2commandsetup L3★6
spartDev/My-Prompt-Manager ↗What it does
Architect and implement feature with tracking
Best for
Full-cycle agile feature delivery: requirements → architecture → Confluence docs → Jira tasks → implementation → metrics.
Inputs
- · feature name
- · feature type (feature|bugfix|refactor|infra)
- · scope (full|frontend|backend|infra)
- · environment
Outputs
- · Confluence documentation
- · Jira epic + tasks
- · implementation + tests
Requires
- · Atlassian MCP (Jira, Confluence)
- · Claude Sonnet API
Preconditions
- · Atlassian MCP connected
- · Jira project configured
- · Confluence accessible
Failure modes
- · Plan rejected → refine and iterate
- · Confluence auth fails → check token
- · Jira rate limit → backoff
- · feature too large → suggest breaking into epics
Trust signals
- · Iterative plan validation loop ('approve' gate)
- · Phase separation (scout → plan → doc → track → build)
- · Jira story points explicit per task
- · Confluence link back to tasks