Workflow Status
Execution Context: This skill runs directly in the PAW session (not a subagent)—simple diagnostic with no context isolation benefit.
Serve as the workflow navigator and historian. Diagnose current workflow state, recommend next actions, and optionally post updates to Issues/PRs.
Reference: Follow Core Implementation Principles from
paw-workflowskill.
Capabilities
- •Diagnose current workflow state from artifacts and git
- •Recommend appropriate next steps
- •Explain PAW process and stages
- •List active work items across workspace
- •Post status updates to Issues/PRs (on explicit request)
Default Behavior
Report status in chat—do NOT post to GitHub unless explicitly asked ("post status to issue", "update the PR summary").
State Detection
Artifact Discovery
Check .paw/work/<work-id>/ for:
- •WorkflowContext.md (required for workflow context)
- •Spec.md, SpecResearch.md (specification stage)
- •CodeResearch.md (research stage)
- •ImplementationPlan.md (planning stage)
- •Docs.md (documentation if separate from implementation)
Note existence vs intentionally skipped (minimal mode skips Spec/Docs).
Phase Counting
Parse ImplementationPlan.md with regex: ^## Phase \d+:
- •Count distinct phase numbers
- •Report: "Phase N of M" or "Phase N (plan shows M phases total)"
- •Never assume total—always verify
Git Status
Determine:
- •Current branch:
git branch --show-current - •Staged/unstaged changes:
git status --porcelain - •Upstream divergence: commits ahead/behind remote
PR Discovery
For prs strategy:
- •Find branches:
<target>_plan,<target>_phase*,<target>_docs - •Query PRs by head branch
- •Capture: URL, state (open/merged/closed), CI status
For local strategy:
- •Focus on target branch and Final PR only
PR Review Comments
When PRs exist:
- •Fetch inline review comments and general discussion
- •Compare comment timestamps vs commit history
- •Summarize: "X comments (Y addressed, Z outstanding)"
Workflow Stage Progression
Map state to guidance:
| State | Recommendation |
|---|---|
| Missing Spec.md + full mode | "Start specification: spec" |
| Spec.md exists, no CodeResearch.md | "Run code research: research" |
| CodeResearch.md exists, no Plan | "Create plan: plan" |
| Plan exists, no phase work | "Begin Phase 1: implement" |
| Phase N complete, Phase N+1 exists | "Continue Phase N+1: implement" |
| All complete | "Create final PR: pr" |
Workflow Mode Behavior
Full Mode
Expect: Spec → Spec Research (optional) → Code Research → Plan → Implementation (multi-phase) → Docs → Final PR
Minimal Mode
Expect: Code Research → Plan → Implementation (single phase) → Final PR Skips: Spec, Spec Research (local strategy enforced)
Custom Mode
Inspect disk to discover actual stages per Custom Workflow Instructions.
Multi-Work Management
When asked "What PAW work items do I have?":
- •Enumerate
.paw/work/directories with WorkflowContext.md - •Report: Work Title, Work ID, target branch, last modified, current stage
- •Sort by most recently modified
Issue/PR Updates (Opt-in Only)
Only post externally when explicitly asked.
Issue comments:
- •Prefix:
**🐾 Status Update 🤖:** - •Include: Artifacts, PRs, phase checklist
PR body updates:
- •Only modify content inside
<!-- BEGIN:AGENT-SUMMARY -->/<!-- END:AGENT-SUMMARY -->block - •Preserve all other text
Never:
- •Modify issue descriptions
- •Assign reviewers
- •Change labels
Help Mode
When asked "What does <stage> do?", provide:
- •Purpose of the stage
- •Required inputs/artifacts
- •Expected outputs
- •Typical duration
- •Command to run
For implementation details (e.g., two-agent pattern, delegation mechanics), reference paw-workflow skill.
For "How do I start?", explain:
- •
PAW: New PAW Workflowcommand - •Parameters (branch, mode, strategy, issue URL)
- •That prompt files generate on demand
Status Dashboard Format
Synthesize findings into sections:
- •Artifacts: Existence and status
- •Phases: Current progress (N of M)
- •Branch & Git: Current state, divergence
- •PRs: Open/merged status, review comments
- •Next Actions: Recommended commands
Guardrails
- •Verify phase count from ImplementationPlan.md—never assume
- •Never mutate issue descriptions or PR content outside summary blocks
- •Never push, merge, or rewrite git history
- •Be idempotent: same state → same summary
- •If required info missing, state blocker and resolution
Completion Response
Report:
- •Current workflow state
- •Recommended next action with command
- •Any blockers or warnings
- •PR/branch status summary