Module 7: Your Daily Workflow

Estimated time: 10 minutes

A Typical Day

Now that you understand the individual systems, here's how they come together in your daily work.

Morning: Triage and Planning

1. Check your Linear board. Look at your assigned issues in To Do and In Progress.
2. Review needs-review issues. These are tickets that Claude ingested but flagged for human review (confidence below 0.7). For each one, decide:
   • Apply ai-plan if you want Claude to write an implementation plan first
   • Apply ai-triaged if the issue is clear enough for Claude to implement directly
   • Apply human-only if it needs manual handling
   • Fix the classification if Claude got the type, platform, or complexity wrong
3. Check for draft PRs. If you applied ai-plan yesterday, there may be plan PRs ready for review.

During Work: Building Features and Fixing Bugs

Starting Work on an Issue

1. Move the Linear issue to In Progress
2. Create a branch following GitFlow naming:

   feature/PL-42-add-auth-middleware
   bugfix/GL-58-fix-date-picker
   hotfix/PL-71-patch-null-crash

3. The branch name must include the Linear issue ID (e.g., PL-42)

Using Claude Code Locally

When working in any registered repo, Claude Code has the full context:

• CLAUDE.md files at root and nested levels
• The l3-lifecycle skill for lifecycle conventions
• The linear-issue-routing skill for issue routing
• The superpowers plugin for brainstorming and planning

You can ask Claude to help with implementation, debugging, and code review right from your terminal.

Filing Bug Reports

Use Marker.io for visual bug reports. Click the widget on any client site, annotate the screenshot, and submit. The ingestion pipeline handles the rest — classification, routing, and GitHub Issue creation.

PR Workflow

1. Open a PR targeting dev (or develop)
2. PR title should match the Linear issue title
3. Description must include Fixes #N to auto-close the GitHub Issue
4. One issue per PR — don't bundle unrelated changes
5. Move the Linear issue to In Review

What Happens After You Open a PR

• Code review — reviewers have 48 hours
• Claude can respond — anyone can comment @claude on the PR to ask questions or request changes (as long as needs-review isn't present)
• After merge — the issue moves to Deployed in Dev, NOT Done

After Meetings

1. Open platform.loop3.ai and go to Meeting Review
2. Click "Extract meetings" to pull unprocessed meetings from the last 24 hours
3. Review the extracted action items:
   • Toggle items on/off
   • Verify or change team assignments
   • Check assignees
4. Click "Create issues" to bulk-create Linear issues
5. The Notion meeting pages are automatically marked as followed-up

End of Day

• Ensure your In Progress issues have linked branches
• Move completed work to In Review (if PR is open) or Deployed in Dev (if merged)
• Don't mark anything as Done unless it's deployed to production and verified

GitFlow Quick Reference

Hard rules:

• Never commit directly to main or dev
• Never force push to protected branches
• Always include the Linear issue ID in the branch name
• One issue per PR

Where to Find Help

Check Your Understanding

Checkpoints

Module Assessment