motovaultpro/.ai/WORKFLOW-PROMPTS.md

MotoVaultPro Workflow Prompts

Ready-to-use prompts for the sprint workflow. Copy and customize as needed.

---

Prompt 1: Start Sprint Work (Pick Up an Issue)

*** ROLE ***
You are senior software architect on MotoVaultPro. Follow the sprint workflow in `.ai/workflow-contract.json`. 

*** ACTION ***
1. Read `.ai/context.json` and `.ai/workflow-contract.json`
2. Check the current sprint milestone via Gitea MCP
3. List issues with `status/ready` label
4. If none ready, show me `status/backlog` issues and recommend which to promote
5. Present the top 3 candidates ranked by priority/size
6. Dispatch multiple agents for their specific tasks. 

---

Prompt 2: Work On a Specific Issue

*** ROLE ***
You are the [feature-agent | frontend-agent | platform-agent]. Read your agent file at `.claude/agents/[agent]-agent.md`.

*** CONTEXT ***
- Read `.ai/workflow-contract.json` for sprint workflow
- Issue to work on: #[NUMBER]

*** ACTION ***
1. Get issue details via `mcp__gitea-mcp__get_issue_by_index`
2. Move issue to `status/in-progress`
3. Create branch `issue-[NUMBER]-[slug]`
4. Implement the acceptance criteria
5. Open PR when complete and move to `status/review`

---

Prompt 3: Quality Validation

*** ROLE ***
You are the quality-agent. Read `.claude/agents/quality-agent.md`.

*** ACTION ***
1. List issues with `status/review` label
2. For each issue awaiting validation:
   - Read acceptance criteria
   - Run all quality gates (linting, type-check, tests, mobile+desktop)
   - Report PASS or FAIL with specific details
3. If PASS: approve PR, move issue to `status/done` after merge
4. If FAIL: comment on issue with required fixes

---

Prompt 4: Sprint Planning Session

*** ROLE ***
You are helping plan Sprint [YYYY-MM-DD].

*** ACTION ***
1. Check if milestone exists via `mcp__gitea-mcp__list_milestones`
2. If not, create it via `mcp__gitea-mcp__create_milestone`
3. List all `status/backlog` issues
4. Recommend issues to promote to `status/ready` for this sprint
5. Consider: dependencies, priority, size, and sprint capacity

---

Prompt 5: Create New Issue

*** ROLE ***
Use the Gitea MCP to create a new issue.

*** CONTEXT ***
- Type: [feature | bug | chore | docs]
- Title: [TITLE]
- Description: [DESCRIPTION]

*** ACTION ***
1. Create issue via `mcp__gitea-mcp__create_issue`
2. Add labels: `type/[type]` and `status/backlog`
3. Optionally assign to current sprint milestone

---

Prompt 6: Sprint Status Report

*** ROLE ***
Generate a sprint status report.

*** ACTION ***
1. Get current sprint milestone via `mcp__gitea-mcp__list_milestones`
2. List all issues in the sprint milestone
3. Group by status label (ready, in-progress, review, done, blocked)
4. Calculate: total issues, completed, remaining, blocked
5. Present summary with any blockers highlighted

---

Prompt 7: End of Sprint Review

*** ROLE ***
Conduct end-of-sprint review for Sprint [YYYY-MM-DD].

*** ACTION ***
1. List all issues that were in this sprint milestone
2. Summarize: completed (status/done), incomplete, blocked
3. For incomplete issues: recommend carry-over to next sprint or return to backlog
4. Create next sprint milestone if it doesn't exist
5. Move carry-over issues to new sprint milestone

---

Quick Reference: MCP Tools

Tool	Purpose
mcp__gitea-mcp__list_repo_issues	List issues (filter by state/milestone)
mcp__gitea-mcp__get_issue_by_index	Get issue details
mcp__gitea-mcp__create_issue	Create new issue
mcp__gitea-mcp__edit_issue	Update issue (title, body, state)
mcp__gitea-mcp__add_issue_labels	Add labels to issue
mcp__gitea-mcp__remove_issue_label	Remove label from issue
mcp__gitea-mcp__replace_issue_labels	Replace all labels on issue
mcp__gitea-mcp__list_milestones	List sprint milestones
mcp__gitea-mcp__create_milestone	Create new sprint
mcp__gitea-mcp__create_branch	Create feature branch
mcp__gitea-mcp__create_pull_request	Open PR
mcp__gitea-mcp__list_repo_pull_requests	List PRs

---

Label Reference

Status Labels (exactly one per issue):

• status/backlog - Not yet ready to work on
• status/ready - Ready to be picked up
• status/in-progress - Currently being worked on
• status/review - PR open, awaiting validation
• status/blocked - Cannot proceed (document blocker)
• status/done - Completed and merged

Type Labels (exactly one per issue):

• type/feature - New capability
• type/bug - Something broken
• type/chore - Maintenance/refactor
• type/docs - Documentation only