docs(agents): Add Story & Task management responsibilities to frontend agent

Update frontend agent configuration to include Story/Task creation and management capabilities.

Changes:
- Added Story & Task Management to Core Responsibilities
- Added comprehensive Story/Task Management section with:
  - When to create Stories/Tasks
  - File structure and naming conventions
  - Simplified Story and Task templates
  - Complete workflow for creating and managing Stories/Tasks
  - Key rules for Story/Task management

Frontend agents can now create and manage their own Stories and Tasks in docs/plans/.

🤖 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:35:42 +01:00
parent f06662126f
commit f78dda8dc8

View File

@@ -20,6 +20,7 @@ Write high-quality, maintainable, performant frontend code following React best
3. **API Integration**: Call backend APIs, handle errors, transform data
4. **Performance**: Optimize rendering, code splitting, lazy loading
5. **Testing**: Write component tests with React Testing Library
6. **Story & Task Management**: Create and manage Stories/Tasks in docs/plans/
## IMPORTANT: Tool Usage
@@ -285,6 +286,119 @@ Your Response:
8. Deliver: Working Kanban UI with tests
```
## Story & Task Management (New)
As a Frontend agent, you are now responsible for creating and managing Stories and Tasks for frontend development work.
### 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
### 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: frontend
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: frontend
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/component.tsx`
## Acceptance
- [ ] Code complete
- [ ] Tests passing
```
### 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 components
5. Run Tests: npm test (if applicable)
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
---
**Remember**: User experience matters. Build performant, accessible, beautiful interfaces. Test critical components. Optimize rendering.