Loop Commands
Manage development loops and PRDs from the command line.
Synopsis#
bootspring loop <command> [options]Description#
The loop system helps you track progress through structured Product Requirements Documents (PRDs). Each PRD contains stories (tasks) that you complete iteratively.
Commands#
| Command | Description |
|---|---|
status | Check PRD status and progress |
next | Get the next story to work on |
complete <id> | Mark a story as complete |
create <name> | Create a new PRD |
bootspring loop status#
Check the current PRD status.
Usage#
bootspring loop status [options]Options#
| Option | Description |
|---|---|
--json | Output as JSON |
--verbose | Show detailed progress |
Example#
bootspring loop statusOutput:
PRD Status: user-authentication
═══════════════════════════════════════════════════════════════════
Progress: 2/5 stories (40%)
▓▓▓▓▓▓▓▓░░░░░░░░░░░░
Stories
───────
✓ story-1 Setup Clerk integration
✓ story-2 Create sign-in page
► story-3 Create sign-up page (IN PROGRESS)
○ story-4 Add protected routes
○ story-5 Implement session management
───────────────────────────────────────────────────────────────────
Next: story-3 - Create sign-up page
When no PRD exists:
No PRD found
Create one with: bootspring loop create <name>
bootspring loop next#
Get the next story to work on.
Usage#
bootspring loop next [options]Options#
| Option | Description |
|---|---|
--json | Output as JSON |
Example#
bootspring loop nextOutput:
Next Story: Create sign-up page
═══════════════════════════════════════════════════════════════════
ID: story-3
Status: pending
Description
───────────
Build the user registration flow with email verification.
Acceptance Criteria
───────────────────
□ Email/password form with validation
□ Password strength indicator
□ Email verification flow
□ Success redirect to dashboard
───────────────────────────────────────────────────────────────────
Complete with: bootspring loop complete story-3
When all stories are complete:
All stories complete! 🎉
Your PRD "user-authentication" is done.
Create a new PRD for your next feature.
bootspring loop complete#
Mark a story as complete.
Usage#
bootspring loop complete <story-id>Example#
bootspring loop complete story-3Output:
Completed: story-3 - Create sign-up page
Progress: 3/5 stories (60%)
▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░
Next story: story-4 - Add protected routes
bootspring loop create#
Create a new PRD.
Usage#
bootspring loop create <name> [options]Options#
| Option | Description |
|---|---|
--template <name> | Use a PRD template |
--stories <n> | Number of placeholder stories |
Example#
bootspring loop create payment-integrationOutput:
Creating PRD: payment-integration
═══════════════════════════════════════════════════════════════════
Created: tasks/prd.json
Default stories:
1. Setup
2. Implementation
3. Testing
Edit tasks/prd.json to customize your stories.
───────────────────────────────────────────────────────────────────
Get started: bootspring loop next
PRD File Format#
PRDs are stored as JSON in tasks/prd.json:
1{
2 "name": "payment-integration",
3 "description": "Add Stripe payment processing",
4 "createdAt": "2024-03-20T10:00:00Z",
5 "stories": [
6 {
7 "id": "story-1",
8 "title": "Set up Stripe",
9 "description": "Install Stripe SDK and configure environment",
10 "status": "completed",
11 "acceptanceCriteria": [
12 "Stripe package installed",
13 "Environment variables configured",
14 "Test mode working"
15 ]
16 },
17 {
18 "id": "story-2",
19 "title": "Create checkout flow",
20 "description": "Build the checkout session creation",
21 "status": "pending",
22 "acceptanceCriteria": [
23 "Checkout API endpoint",
24 "Redirect to Stripe",
25 "Success/cancel handling"
26 ]
27 },
28 {
29 "id": "story-3",
30 "title": "Handle webhooks",
31 "description": "Process Stripe webhook events",
32 "status": "pending",
33 "acceptanceCriteria": [
34 "Webhook endpoint",
35 "Signature verification",
36 "Event handling"
37 ]
38 }
39 ]
40}Configuration#
PRD Path#
1// bootspring.config.js
2module.exports = {
3 paths: {
4 prd: 'tasks/prd.json', // Default
5 },
6};Workflow Integration#
With Agents#
1# Get next story
2bootspring loop next
3
4# Use agent for implementation
5bootspring agent invoke frontend-expert "Implement sign-up page with Clerk"
6
7# Complete when done
8bootspring loop complete story-3With Skills#
1# Get next story
2bootspring loop next
3
4# Apply relevant skill
5bootspring skill apply auth/clerk
6
7# Complete
8bootspring loop complete story-1With Workflows#
1# Start a workflow
2bootspring workflow start feature-development
3
4# Track with loop
5bootspring loop create user-dashboard
6bootspring loop next
7# ... work through storiesBest Practices#
Write Clear Stories#
Each story should be:
- Specific and actionable
- Completable in a few hours
- Have clear acceptance criteria
1{
2 "id": "story-1",
3 "title": "Add user avatar upload",
4 "description": "Allow users to upload profile pictures",
5 "acceptanceCriteria": [
6 "File input with image preview",
7 "Max 5MB file size",
8 "Crop/resize to 200x200",
9 "Upload to S3",
10 "Update user record"
11 ]
12}One Feature Per PRD#
Keep each PRD focused on a single feature:
user-authentication- Auth-related storiespayment-integration- Payment storiesuser-dashboard- Dashboard stories
Update Progress Regularly#
Mark stories complete as you finish them for accurate tracking.
Archive Completed PRDs#
When done, archive the PRD:
mv tasks/prd.json tasks/archive/user-auth-prd.json
bootspring loop create next-featureRelated#
- bootspring_loop - MCP tool reference
- Todo Commands - Simple task management
- Workflow Commands - Workflow management