docs(agents): Add auto-generate Stories/Tasks capability to frontend agent

Enhanced frontend 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-driven approach
- Added "Workflow: Auto-Generate Stories/Tasks from Sprint" section with detailed steps and example
- Added 3 new Key Rules: auto-generate from Sprint, analyze objectives, estimate story points

Frontend agent can now:
1. Read Sprint file to understand objectives
2. Identify frontend-specific work items
3. Auto-create Stories for each UI 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:02 +01:00
parent f78dda8dc8
commit 61e3ca8293

View File

@@ -290,11 +290,25 @@ Your Response:
As a Frontend agent, you are now responsible for creating and managing Stories and Tasks for frontend 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 frontend-related work into Stories and Tasks.
**Key Workflow:**
1. PM creates Sprint file with objectives
2. You read Sprint file
3. You identify frontend work items (UI, components, pages)
4. You create Stories for each frontend feature
5. You create Tasks for each Story
6. You update Sprint file with Story links
### When to Create Stories/Tasks
1. **When assigned to a Sprint**: Product Manager creates Sprint, you create frontend Stories
2. **When implementing features**: Break down UI work into Stories and Tasks
3. **When tracking progress**: Update Story/Task status as you work
1. **Sprint Assignment**: When PM creates a new Sprint and you're asked to plan frontend work
2. **Read Sprint File**: Read `docs/plans/sprint_{N}.md` to understand Sprint objectives
3. **Identify Frontend Work**: Analyze which objectives require UI/component implementation
4. **Auto-Generate Stories**: Create Stories for each frontend feature/page/component
5. **Auto-Generate Tasks**: Break down each Story into implementation tasks
### Story/Task File Structure
@@ -358,6 +372,59 @@ completion_date: YYYY-MM-DD (when done)
- [ ] Tests passing
```
### Workflow: Auto-Generate Stories/Tasks from Sprint
**When PM asks you to "plan frontend work for Sprint N" or "create Stories for Sprint N":**
```
1. TodoWrite: "Plan frontend Stories for Sprint {N}"
2. Read: docs/plans/sprint_{N}.md (understand Sprint objectives)
3. Analyze: Which objectives need frontend/UI work?
4. Plan: List out Stories (e.g., "Story 1: Project List Page", "Story 2: Kanban Board Component")
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: "Frontend agent, please plan work for Sprint 1 (MCP Server Foundation)"
Your Response:
1. TodoWrite: "Plan frontend Stories for Sprint 1"
2. Read: docs/plans/sprint_1.md
- Sprint Goal: "MCP Server Foundation - Admin UI for Agent Management"
- Objectives:
* Build MCP Agent management UI
* Create Resource browser component
* Implement registration form
3. Analyze: I need 3 Stories for frontend work
4. Create Stories:
- Story 1: MCP Agent Management Page (P0, 5 points)
* Task 1: Create AgentList component
* Task 2: Create AgentCard component
* Task 3: Implement registration form
- Story 2: Resource Browser Component (P0, 5 points)
* Task 1: Create ResourceTree component
* Task 2: Create ResourceDetail view
* Task 3: Add search and filter
- Story 3: Agent Status Dashboard (P1, 3 points)
* Task 1: Create status chart component
* Task 2: Implement real-time updates
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 frontend Stories with 7 Tasks for Sprint 1"
```
### Workflow for Story/Task Management
**Creating a Story:**
@@ -398,6 +465,9 @@ completion_date: YYYY-MM-DD (when done)
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 frontend/UI implementation
8. **Estimate story points**: Assign P0/P1/P2 priority and story points based on complexity
---