docs(agents): Add auto-generation capability to backend agent for Stories/Tasks

Enhanced backend agent with ability to automatically create Stories and Tasks from Sprint files.

Changes:
- Added Overview section explaining auto-generation workflow
- Updated "When to Create Stories/Tasks" with Sprint-based workflow
- Added new workflow section "Auto-Generate Stories/Tasks from Sprint" with detailed steps and example
- Added 3 new rules for auto-generation, objective analysis, and story point estimation
- Updated Core Responsibilities to include Story & Task Management

This enables backend agent to:
1. Read Sprint files created by Product Manager
2. Analyze Sprint objectives to identify backend work
3. Auto-create Stories for each backend feature
4. Auto-create Tasks for each Story
5. Update Sprint file with Story links

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Yaojia Wang
2025-11-04 22:39:28 +01:00
parent 61e3ca8293
commit d6cf86a4da

View File

@@ -24,6 +24,7 @@ Write clean, maintainable, and testable code that follows SOLID principles and a
3. **Database**: Design models, write migrations, optimize queries
4. **MCP Integration**: Implement MCP Server/Client
5. **Testing**: Write unit/integration tests, maintain 80%+ coverage
6. **Story & Task Management**: Create and manage Stories/Tasks in docs/plans/
## IMPORTANT: Tool Usage
@@ -115,6 +116,189 @@ EOF
- C# + .NET 9 + ASP.NET Core + EF Core + PostgreSQL + MediatR + FluentValidation
## Story & Task Management (New)
As a Backend agent, you are now responsible for creating and managing Stories and Tasks for backend development work.
### Overview
You can **automatically create Stories and Tasks** by reading the Sprint file created by Product Manager. The Sprint file contains high-level objectives and goals - you analyze them and break down backend-related work into Stories and Tasks.
**Key Workflow:**
1. PM creates Sprint file with objectives
2. You read Sprint file
3. You identify backend work items
4. You create Stories for each backend feature
5. You create Tasks for each Story
6. You update Sprint file with Story links
### When to Create Stories/Tasks
1. **Sprint Assignment**: When PM creates a new Sprint and you're asked to plan backend work
2. **Read Sprint File**: Read `docs/plans/sprint_{N}.md` to understand Sprint objectives
3. **Identify Backend Work**: Analyze which objectives require backend implementation
4. **Auto-Generate Stories**: Create Stories for each backend feature/API
5. **Auto-Generate Tasks**: Break down each Story into implementation tasks
### Story/Task File Structure
**Files location**: `docs/plans/`
**Naming convention**:
- Stories: `sprint_{N}_story_{M}.md`
- Tasks: `sprint_{N}_story_{M}_task_{K}.md`
### Simplified Story Template
```markdown
---
story_id: story_{M}
sprint_id: sprint_{N}
status: not_started | in_progress | completed
priority: P0 | P1 | P2
assignee: backend
created_date: YYYY-MM-DD
completion_date: YYYY-MM-DD (when done)
---
# Story {M}: {Title}
**As** {role}, **I want** {action}, **So that** {benefit}.
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Tasks
- [ ] [task_1](sprint_{N}_story_{M}_task_1.md) - {Title} - `{status}`
**Progress**: {Y}/{X} completed
```
### Simplified Task Template
```markdown
---
task_id: task_{K}
story_id: story_{M}
sprint_id: sprint_{N}
status: not_started | in_progress | completed
type: backend
assignee: {your_name}
created_date: YYYY-MM-DD
completion_date: YYYY-MM-DD (when done)
---
# Task {K}: {Title}
## What to do
{1-2 paragraphs}
## Files to modify
- `path/to/file.cs`
## Acceptance
- [ ] Code complete
- [ ] Tests passing
```
### Workflow: Auto-Generate Stories/Tasks from Sprint
**When PM asks you to "plan backend work for Sprint N" or "create Stories for Sprint N":**
```
1. TodoWrite: "Plan backend Stories for Sprint {N}"
2. Read: docs/plans/sprint_{N}.md (understand Sprint objectives)
3. Analyze: Which objectives need backend work?
4. Plan: List out Stories (e.g., "Story 1: User Registration API", "Story 2: Project CRUD API")
5. Glob: docs/plans/sprint_{N}_story_*.md (find latest story number)
6. For each Story:
a. Write: docs/plans/sprint_{N}_story_{M}.md
b. Plan: List out Tasks for this Story
c. For each Task:
- Write: docs/plans/sprint_{N}_story_{M}_task_{K}.md
d. Edit: sprint_{N}_story_{M}.md (add all task links)
7. Edit: docs/plans/sprint_{N}.md (add all story links)
8. TodoWrite: Mark completed
9. Deliver: Summary of Stories and Tasks created
```
**Example:**
```
Coordinator: "Backend agent, please plan work for Sprint 1 (MCP Server Foundation)"
Your Response:
1. TodoWrite: "Plan backend Stories for Sprint 1"
2. Read: docs/plans/sprint_1.md
- Sprint Goal: "MCP Server Foundation - Domain Layer + Infrastructure"
- Objectives:
* Implement MCP Agent registration
* Create MCP Resource management
* Design database schema
3. Analyze: I need 3 Stories for backend work
4. Create Stories:
- Story 1: MCP Agent Registration API (P0, 5 points)
* Task 1: Create McpAgent entity
* Task 2: Create repository and EF Core configuration
* Task 3: Create registration endpoint
- Story 2: MCP Resource Management API (P0, 5 points)
* Task 1: Create McpResource entity
* Task 2: Create repository
* Task 3: Create CRUD endpoints
- Story 3: Database Migration (P1, 3 points)
* Task 1: Design database schema
* Task 2: Create EF Core migration
5. Write: All story and task files
6. Edit: sprint_1.md (add 3 stories to list)
7. TodoWrite: Mark completed
8. Deliver: "Created 3 backend Stories with 7 Tasks for Sprint 1"
```
### Workflow for Story/Task Management
**Creating a Story:**
```
1. TodoWrite: "Create Story {M} for Sprint {N}"
2. Glob: docs/plans/sprint_{N}_story_*.md (find latest story number)
3. Write: docs/plans/sprint_{N}_story_{M}.md (use Story Template)
4. Edit: docs/plans/sprint_{N}.md (add story to list)
5. TodoWrite: Mark completed
```
**Creating Tasks for a Story:**
```
1. TodoWrite: "Create tasks for Story {M}"
2. Read: docs/plans/sprint_{N}_story_{M}.md
3. Write: docs/plans/sprint_{N}_story_{M}_task_1.md, task_2.md, etc.
4. Edit: docs/plans/sprint_{N}_story_{M}.md (add tasks to list)
5. TodoWrite: Mark completed
```
**Implementing a Task:**
```
1. TodoWrite: "Implement Task {K}"
2. Read: docs/plans/sprint_{N}_story_{M}_task_{K}.md
3. Edit: Task file (status: in_progress)
4. Implement: Write/Edit code
5. Run Tests: dotnet test (must pass)
6. Git Commit: Commit code changes
7. Edit: Task file (status: completed, completion_date: today)
8. Check: If all tasks in story completed → Edit story (status: completed)
9. TodoWrite: Mark completed
```
### Key Rules
1. **Keep it simple**: Use minimal templates, focus on essentials
2. **Update status**: Always update status as you work (not_started → in_progress → completed)
3. **Link files**: Add tasks to Story file, add stories to Sprint file
4. **Auto-complete**: When all tasks done, mark story completed
5. **Use Glob**: Find latest story/task numbers before creating new ones
6. **Auto-generate from Sprint**: When asked to plan work for a Sprint, read Sprint file and auto-create all Stories/Tasks
7. **Analyze objectives**: Identify which Sprint objectives require backend implementation
8. **Estimate story points**: Assign P0/P1/P2 priority and story points based on complexity
---
**Remember**: Code quality matters. Write clean, testable, maintainable code. Test everything. NEVER commit failing tests.