$ recombobulate _
home / tips / give-claude-a-user-story-and-let-it-build-the-complete-feature-end-to-end
70

Give Claude a User Story and Let It Build the Complete Feature End-to-End

recombobulate @recombobulate · Mar 29, 2026 · Workflows
give-claude-a-user-story-and-let-it-build-the-complete-feature-end-to-end

User stories describe what users need. Claude turns that into everything the feature requires — from database to UI, in one prompt.

"As a user, I want to save products to a wishlist so I can buy them later.
Build the complete feature."

Claude reads your project, understands the stack, and builds every layer:

  • Database — migration for the wishlist table with proper relationships
  • Model — Eloquent model with relationships, scopes, and accessors
  • Controller — endpoints to add, remove, and list wishlist items
  • Routes — properly grouped and authenticated route definitions
  • UI — add-to-wishlist button, wishlist page, empty state
  • Validation — request validation for all inputs
  • Tests — feature tests covering the full workflow

The key is writing a good user story:

# Be specific about the scope
"As an admin, I want to invite team members by email. They should receive 
an invitation link that expires in 48 hours, and I should see pending 
invitations with the ability to revoke them."

# Include acceptance criteria for better results
"As a user, I want to filter products by price range, category, and rating.
Acceptance criteria:
- Filters combine with AND logic
- URL updates with filter params so results are shareable
- Filters persist when paginating
- Show active filter count on the filter button"

# Specify the tech if it matters
"As a user, I want real-time notifications when someone comments on my post.
Use Livewire events, not WebSockets."

For complex features, combine user stories with the phased approach:

"Build these three user stories in order, testing each before moving to the next:
1. As a user, I want to create a team
2. As a team owner, I want to invite members
3. As a member, I want to see and accept invitations"

Claude follows your project's existing patterns — if your controllers use form requests, your tests use factories, and your routes use resource controllers, the new feature matches.

User stories are how you think about features. Let Claude read the story and write the implementation — from database to UI in one conversation.

via Claude Code

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 day ago