Sprint Status
Skill ActiveTrack parallel work sessions and prevent confusion across multiple Claude Code instances. Every major step ends with a status line. Every question re-states project, branch, and task.
To prevent confusion and maintain context when working across multiple parallel Claude Code instances by establishing clear session identification and status reporting.
Features
- Session identification header
- Structured status lines (COMPLETE, COMPLETE_WITH_NOTES, BLOCKED, NEEDS_INFO)
- Guidance on detecting parallel sessions
- Patterns for managing parallel work
- Sprint dashboard compilation
Use Cases
- When running multiple Claude Code sessions concurrently for different tasks or features.
- To ensure clear communication and context when collaborating with AI on parallel development streams.
- To maintain a consistent understanding of progress and blockers across different AI-driven tasks.
- To avoid applying feedback or changes to the wrong Claude Code instance.
Non-Goals
- Managing the actual code or files within sessions.
- Providing a project management tool beyond session tracking.
- Automating commit or merge processes.
Workflow
- Identify if multiple sessions are active.
- Include session identification header in responses.
- End major steps with a status line.
- Provide clear status (COMPLETE, COMPLETE_WITH_NOTES, BLOCKED, NEEDS_INFO).
- Compile sprint status view when requested.
Practices
- Workflow Management
- Collaboration
- Status Reporting
Prerequisites
- Claude Code environment
Versioning
- warning:Release ManagementNo explicit versioning (e.g., in SKILL.md frontmatter, package.json, or GitHub releases) is apparent, and installation references 'main'.
Installation
First, add the marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowQuality Score
Trust Signals
Similar Extensions
Agent Teams
100Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
Wrap Up Ritual
100End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.
Obey
100Show all active rules. Use when the user says "/rules", "show rules", "list rules", "what are my rules", or wants to see their current persistent instructions.
Team Lead Persona
100Lead a team — run standups, coordinate tasks, and communicate.
Ce Brainstorm
100Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.
Public Google Drive
100Create public Google Docs or Google Sheet files without requiring OAuth. Use this skill to create and edit Google Docs and Sheets, no Google sign-in required. Documents are viewable at shareable links. Registration is automatic on first use.