You have clear requirements for 3 well-defined features. Let the AI run a full sprint with minimal human intervention.
⏱ ~15 min · Hands-on
You have 3 well-defined features for a user profile page: avatar upload, bio editing, and account deletion. The requirements are clear, the patterns are established, and the codebase is familiar. This is a perfect candidate for autonomous mode — the AI handles the full sprint while you review at key checkpoints.
Autonomous mode requires unambiguous requirements. Vague inputs produce vague outputs.
Build the user profile management feature:
1. Profile Page — display user info (name, email, bio, avatar)
2. Avatar Upload — upload and crop profile picture (max 2MB, jpg/png)
3. Bio Editing — inline edit bio text (max 500 chars, markdown supported)
4. Account Deletion — soft-delete with 30-day recovery window
Tech stack: React frontend, Node/Express API, PostgreSQL
Patterns: follow existing UserService, use Zod validation
Auth: JWT, user can only edit their own profileThe AI writes user stories following INVEST criteria with clear acceptance criteria.
/agile-story-create📋 PROF-001: User Profile Page
As a user, I want to view my profile page
so that I can see my account information.
AC:
✅ Displays name, email, bio, and avatar
✅ Shows "Edit" buttons for editable fields
✅ Responsive layout (mobile + desktop)
✅ Returns 404 for non-existent users
📋 PROF-002: Avatar Upload
As a user, I want to upload a profile picture
so that other users can recognize me.
AC:
✅ Accepts JPG and PNG only
✅ Rejects files over 2MB with clear error
✅ Provides crop interface before saving
✅ Stores in S3, serves via CDN
✅ Falls back to initials avatar if none set
📋 PROF-003: Account Deletion
As a user, I want to delete my account
so that I can remove my data from the platform.
AC:
✅ Requires password confirmation
✅ Soft-deletes (sets deleted_at timestamp)
✅ 30-day recovery window before hard delete
✅ Sends confirmation email
✅ Immediately logs user out/agile-story-estimateStory Estimates:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PROF-001 Profile Page 3 pts (display only, known patterns)
PROF-002 Avatar Upload 5 pts (file handling, S3, crop UI)
PROF-003 Account Deletion 3 pts (soft-delete, email, auth check)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total: 11 story points/agile-sprint-planningSprint Planning — Sprint 4
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Goal: "Users can manage their profile"
Capacity: 11 story points
Duration: 1 week
Stories: PROF-001 (3pts), PROF-002 (5pts), PROF-003 (3pts)
Execution Order:
1. PROF-001 (Profile Page) — foundation for other stories
2. PROF-002 (Avatar Upload) — highest complexity
3. PROF-003 (Account Deletion) — independent, last
✅ Sprint committedThe AI chains all commands for each story: plan, branch, TDD, CI, PR, DoD check. Here's how it handles PROF-001:
/agile-story-planPlan confidence: 9/10
Implementation plan:
1. Create ProfilePage component + route
2. Add GET /api/users/:id/profile endpoint
3. Add ProfileService with getProfile method
4. Write unit + integration tests/agile-code-branch→ Created branch: feature/PROF-001-profile-page from develop/agile-code-tddRED: 6 tests written (API + component + service)
GREEN: 6 tests passing — all AC covered
REFACTOR: Extracted ProfileCard sub-component/agile-code-ciBuild ✅ | Tests 162/162 ✅ | Lint ✅ | Coverage 85% ✅/agile-code-prPR #67: feat(profile): add user profile page
Files changed: 8 | +240 -12/agile-code-pr-reviewReview: ✅ Approved
- Clean component structure
- Proper error handling for missing users
- Good test coverage/agile-story-dodDefinition of Done — PROF-001:
✅ All acceptance criteria met
✅ Tests passing (unit + integration)
✅ Code reviewed and approved
✅ CI pipeline green
✅ No security warnings
→ DONEThe AI repeats this cycle for PROF-002 and PROF-003:
/agile-story-plan → confidence 9/10
/agile-code-branch → Created branch: feature/PROF-002-avatar-upload from develop
/agile-code-tdd → RED: 8 tests | GREEN: 8 passing | REFACTOR: done
/agile-code-ci → all green
/agile-code-pr → PR #68: feat(profile): avatar upload with crop
/agile-code-pr-review → ✅ Approved (1 minor suggestion applied)
/agile-story-dod → ✅ DONE/agile-story-plan → confidence 9/10
/agile-code-branch → Created branch: feature/PROF-003-account-deletion from develop
/agile-code-tdd → RED: 7 tests | GREEN: 7 passing | REFACTOR: done
/agile-code-ci → all green
/agile-code-pr → PR #69: feat(profile): soft-delete account
/agile-code-pr-review → ✅ Approved
/agile-story-dod → ✅ DONEAutonomous does not mean unsupervised. The AI pauses here for you to review.
The AI presents its work. You review the code, PRs, and test coverage. Autonomous mode handles execution, but humans own the final approval.
Sprint 4 — Autonomous Execution Complete
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Stories Completed: 3/3
Points Delivered: 11/11
PRs Ready for Merge:
PR #67: feat(profile): user profile page ✅ reviewed
PR #68: feat(profile): avatar upload + crop ✅ reviewed
PR #69: feat(profile): soft-delete account ✅ reviewed
Test Summary:
New tests written: 21
Total tests passing: 177/177
Coverage: 86% (was 84%)
Awaiting: YOUR approval to merge all PRs to developAfter human approval, the AI runs the sprint review.
/agile-sprint-reviewSprint Review — Sprint 4
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Goal: "Users can manage their profile"
Goal Met: ✅ Yes
Stories Done: 3/3 (100%)
Points: 11/11 delivered
Velocity: 11 pts (team avg: 10 pts)
Demo:
✅ Profile page renders with user data
✅ Avatar uploads, crops, and displays via CDN
✅ Account deletion soft-deletes with recovery window
Stakeholder Feedback: Approved/agile-sprint-retroSprint Retrospective — Sprint 4
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
What went well:
+ Autonomous execution completed all 3 stories
+ TDD caught a file validation edge case early
+ Clear requirements = no re-planning needed
What to improve:
- Avatar crop library added as new dependency (should flag)
- Could parallelize PROF-001 and PROF-003 (independent)
Action items:
📋 Add dependency review to autonomous checklist
📋 Enable parallel story execution for independent storiesAutonomous mode is powerful but bounded. These safety rails prevent runaway execution.
The AI stops and waits for human approval before proceeding with:
The AI continues but flags these for human attention:
Hard limits prevent infinite retries:
/agile-story-create — AI writes INVEST stories with acceptance criteria/agile-story-estimate + /agile-sprint-planning — AI plans a full sprint/agile-story-plan → /agile-code-branch → /agile-code-tdd → /agile-code-ci → /agile-code-pr → /agile-code-pr-review → /agile-code-merge → /agile-story-dod/agile-sprint-review — reporting velocity and demo results/agile-sprint-retro — capturing what worked and what to improveWhen does autonomous mode pause for human review?