Skip to main content

Common Workflows

This guide shows you how to use Stardust to manage work without the overhead of traditional project management tools. No standups. No story pointing. No velocity tracking. Just clarity about what matters.
Strategic Laziness in Action: These workflows minimize ceremony and maximize outcomes.

Daily Workflows

Morning Planning

Start your day by focusing on what actually matters:
1

Check what's ready

stardust tasks ready --owner @me
This shows only unblocked tasks assigned to you, sorted by priority.
2

Get AI recommendations

stardust tasks prioritize
AI analyzes urgency, impact, and context to suggest what you should work on first.
3

Pick one thing

Don’t multitask. Choose one task and start:
stardust task start tk-001
4

Delete what doesn't matter

If a task has been sitting for weeks, question whether it’s actually important:
stardust task delete tk-002 --force
The best work is the work you don’t do.
Limit work in progress: Focus on finishing tasks, not starting them. One task at a time beats ten tasks at 10%.

End-of-Day Review

Close the day by updating status and clearing your mind:
stardust task done tk-001
If you’re stuck, say so immediately:
stardust task update tk-002 --status blocked \
  --description "Waiting on design feedback"
Review what’s coming up:
stardust tasks ready --due-before tomorrow

Weekly Review

Every week, question your commitments:
1

Review open tasks

stardust tasks list --status todo --owner @me
2

Identify stale tasks

Look for tasks with no recent activity. Ask: “Does this still matter?”
3

Delete or defer

Be ruthless. If it’s been sitting for weeks, either do it this week or delete it.
4

Check blocked items

stardust tasks list --status blocked
Follow up on blockers or reassess if they’re still relevant.

Priority Management

When Everything Feels Urgent

Use AI triage to cut through the noise:
stardust tasks prioritize
What AI considers:
  • Due dates and deadlines
  • Priority levels
  • Tasks blocking other work
  • How long tasks have been open
What you get:
Do Now
│ Fix auth bug - Critical, due today

Do Next
│ Review roadmap - High priority, due tomorrow

Consider Deleting
│ Reorganize files - No activity in 3 months

The One Thing

When overwhelmed, ask for the single most important task:
stardust tasks next
Focus only on that until it’s done.

Shell Integration

Useful Aliases

Add these to your .zshrc or .bashrc:
# Morning routine
alias morning="stardust tasks ready --owner @me --priority high,critical"

# Quick add
alias ta="stardust add"

# What's next
alias next="stardust tasks next"

# Mark done
alias done="stardust task done"

Daily Startup Script

Create a morning routine:
#!/bin/bash
# ~/.stardust-morning

echo "Good morning! Here's what matters today:"
echo ""
stardust tasks ready --owner @me --limit 5
echo ""
echo "AI recommendation:"
stardust tasks next

Best Practices

Do Less

Question every task. Delete liberally. The best work is the work you don’t do.

Own Everything

Every task has exactly one owner. No shared accountability.

Update Promptly

Status should always reflect reality. Update as you work.

Ship to Learn

Production is truth. Bias toward action over planning.

Anti-Patterns to Avoid

Don’t use Stardust as a wishlist. Every task should have an owner, a rough timeframe, and a reason to exist.
Don’t batch status updates. Update immediately when things change. Your future self will thank you.
Don’t ignore AI recommendations. They’re based on real data. At least consider them before overriding.

Example: Developer’s Day

Here’s how a typical day might look: 8:30 AM - Morning check
stardust tasks ready --owner @me
See 3 tasks: auth bug (critical), code review (high), update docs (medium) 8:35 AM - Start critical task
stardust task start tk-001  # auth bug
11:00 AM - Done with auth bug
stardust task done tk-001
11:05 AM - Quick capture
stardust add "Follow up on deployment questions"
11:10 AM - Start next task
stardust task start tk-002  # code review
12:30 PM - Blocked
stardust task update tk-002 --status blocked \
  --description "Waiting for additional context from PR author"
12:35 PM - Pivot to something else
stardust tasks ready
stardust task start tk-003  # update docs
5:30 PM - End of day review
stardust tasks list --owner @me --status in_progress
Update status, note blockers, clear head for tomorrow.

Next Steps