/status
Check project progress, active tasks, learning stats, and career portfolio
$ npx -y skills add DanielPodolsky/ownyourcode --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/status
Context preview
What this command does when you run it.
Check project progress, active tasks, learning stats, and career portfolio
Command definition
status.mdname: status
description: Check project progress, active tasks, learning stats, and career portfolio
allowed-tools: Read, Glob, Grep, Bash
/own:status
> ⚠️ **PLAN MODE WARNING:** Toggle plan mode off before running this command (`shift+tab`). OwnYourCode commands don't work correctly with plan mode.
Get a comprehensive status report on project progress and learning growth.
Overview
This command provides: 1. **Roadmap Progress** — Where you are in the project 2. **Active Specs** — Current work in progress 3. **Learning Stats** — Skills and patterns documented 4. **Recent Activity** — Last commits and changes 5. **Career Stats** — Interview stories and resume bullets collected (if enabled)
**Profile-Aware Behavior:** Check `.claude/ownyourcode-manifest.json` for `profile.settings.career_focus`:
- If `"full-extraction"` or `"tips-only"` → Show Career Stats section
- If `"none"` → **Hide Career Stats section entirely**
---
Execution Flow
Step 1: Gather Data
Read project files to compile status. This step is **read-only** — `/own:status` never writes to `dashboard-data.js`.
ownyourcode/dashboard/dashboard-data.js — window.PROJECT: roadmap, specs, tasks, DoD (the SDD source of truth)
ownyourcode/career/stories/ — Interview stories
learning/LEARNING_REGISTRY.md — Learning flywheel data
.claude/skills/learned/ — Auto-generated skills
From `window.PROJECT`, compute (do not store — these are derived):
- **Roadmap progress** = phases grouped by `status` (roadmap-only / specced / complete)
- **Active phase** = first phase with `status !== "complete"`
- **Per-phase task progress** = `tasks.filter(t => t.done).length / tasks.length`
- **DoD progress** = `dod.filter(d => d.done).length / dod.length`
Also check git activity:
git log --oneline -10 --since="1 week ago"
---
Step 2: Generate Status Report
Roadmap Progress
Derive each phase's line from its `status` and (if specced) its task progress:
## Roadmap Progress
Phase 1: Foundation ██████████ complete
Phase 2: Logging █████░░░░░ specced · 3/5 tasks
Phase 3: Visualization ░░░░░░░░░░ roadmap-only
Overall: 1 complete · 1 specced · 1 planned (of 3 phases)
---
Active Work
From the active phase (first with `status !== "complete"`) in `window.PROJECT`:
## Active Phase
### Phase [n]: [name] — [status]
Open the Tasks tab in ownyourcode/dashboard/dashboard.html for the full kanban.
Tasks:
- [x] [done task] (id 1.1)
- [ ] [next undone task] (id 2.1) <-- YOU ARE HERE
- [ ] [pending task] (id 2.2)
Progress: 2/4 tasks (50%)
The `[x]`/`[ ]` above is just the terminal rendering of each task's `done` flag — the source of truth is `window.PROJECT`, not a Markdown file.
If the active phase is still `roadmap-only` (not yet specced):
## Active Phase
### Phase [n]: [name] — roadmap-only
Not specced yet. Run /own:feature to generate its spec, design & tasks.
If every phase is `complete`:
## Active Phase
All phases complete 🎉 Run /own:feature to plan what's next.
---
Learning Stats (NEW)
## Learning Growth
Patterns Documented: ███░░░░░░░ 4
Failures Documented: █░░░░░░░░░ 2
Total Insights: ████░░░░░░ 6
Domains Explored:
• Auth: ████████░░ (8 learnings)
• Forms: ████░░░░░░ (4 learnings)
• API: ██░░░░░░░░ (2 learnings)
• Database: ░░░░░░░░░░ (0 learnings)
Current Level: ⭐⭐⭐ (Intermediate)
Last Learning: "Always initialize array state as [] not undefined" (3 days ago)
Competency levels:
- ⭐ Beginner (0-5 learnings)
- ⭐⭐ Developing (6-15 learnings)
- ⭐⭐⭐ Intermediate (16-30 learnings)
- ⭐⭐⭐⭐ Advanced (31-50 learnings)
- ⭐⭐⭐⭐⭐ Expert (50+ learnings)
---
Recent Activity
## Recent Activity (Last 7 Days)
Commits:
- feat(auth): implement login form (2 days ago)
- fix(api): resolve CORS issue (3 days ago)
- chore(deps): update dependencies (5 days ago)
Files Changed: 12
Lines Added: 342
Lines Removed: 89
---
Career Stats
**⚠️ Profile Check:** Read `.claude/ownyourcode-manifest.json` → `profile.settings.career_focus`
- If `"none"` → **SKIP THIS SECTION ENTIRELY**
- If `"full-extraction"` or `"tips-only"` → Show section below
## Career Portfolio
Interview Stories: 3
- "Debugging race condition in form submission"
- "Implementing JWT refresh rotation"
- "Building accessible navigation"
Resume Bullets: 3
- "Engineered secure authentication..."
- "Resolved critical race condition..."
- "Developed WCAG-compliant navigation..."
Each feature you complete adds to your interview arsenal!
---
Step 3: Recommendations
Based on status, provide personalized recommendations:
If they have active work:
## Next Steps
You're currently working on: [Feature Name]
Current task: [Task description]
Suggested action: Run /own:guide to continue implementing
If no active work:
## Next Steps
Your roadmap shows these pending phases:
- Phase 2: Core Features
Suggested action: Run /own:feature to start your next feature
If they've been inactive:
## Welcome Back!
It's been [X days] since your last commit.
You were working on: [Feature]
Want to pick up where you left off?
Run /own:guide to continue, or /own:feature for something new.
If low learning stats:
## Learning Flywheel Reminder
You have [X] learnings documented.
Run /own:retro after completing tasks to capture insights.
The more you document, the smarter /own:advise becomes!
---
Step 4: Visual Status
**Profile-Aware Visual:**
- Read `profile.settings.career_focus` from manifest
- If `"none"` → Omit CAREER STATS section from visual
Create a visual summary:
┌─────────────────────────────────────────────────────────────┐
│ PROJECT STATUS │
├─────────────────────────────────────────────────────────────┤
│ Project: [Name]
Read more
name: status description: Check project progress, active tasks, learning stats, and career portfolio allowed-tools: Read, Glob, Grep, Bash
/own:status
> ⚠️ **PLAN MODE WARNING:** Toggle plan mode off before running this command (`shift+tab`). OwnYourCode commands don't work correctly with plan mode.
Get a comprehensive status report on project progress and learning growth.
Overview
This command provides: 1. **Roadmap Progress** — Where you are in the project 2. **Active Specs** — Current work in progress 3. **Learning Stats** — Skills and patterns documented 4. **Recent Activity** — Last commits and changes 5. **Career Stats** — Interview stories and resume bullets collected (if enabled)
**Profile-Aware Behavior:** Check `.claude/ownyourcode-manifest.json` for `profile.settings.career_focus`:
- If `"full-extraction"` or `"tips-only"` → Show Career Stats section
- If `"none"` → **Hide Career Stats section entirely**
---
Execution Flow
Step 1: Gather Data
Read project files to compile status. This step is **read-only** — `/own:status` never writes to `dashboard-data.js`.
ownyourcode/dashboard/dashboard-data.js — window.PROJECT: roadmap, specs, tasks, DoD (the SDD source of truth) ownyourcode/career/stories/ — Interview stories learning/LEARNING_REGISTRY.md — Learning flywheel data .claude/skills/learned/ — Auto-generated skills
From `window.PROJECT`, compute (do not store — these are derived):
- **Roadmap progress** = phases grouped by `status` (roadmap-only / specced / complete)
- **Active phase** = first phase with `status !== "complete"`
- **Per-phase task progress** = `tasks.filter(t => t.done).length / tasks.length`
- **DoD progress** = `dod.filter(d => d.done).length / dod.length`
Also check git activity:
git log --oneline -10 --since="1 week ago"
---
Step 2: Generate Status Report
Roadmap Progress
Derive each phase's line from its `status` and (if specced) its task progress:
## Roadmap Progress Phase 1: Foundation ██████████ complete Phase 2: Logging █████░░░░░ specced · 3/5 tasks Phase 3: Visualization ░░░░░░░░░░ roadmap-only Overall: 1 complete · 1 specced · 1 planned (of 3 phases)
---
Active Work
From the active phase (first with `status !== "complete"`) in `window.PROJECT`:
## Active Phase ### Phase [n]: [name] — [status] Open the Tasks tab in ownyourcode/dashboard/dashboard.html for the full kanban. Tasks: - [x] [done task] (id 1.1) - [ ] [next undone task] (id 2.1) <-- YOU ARE HERE - [ ] [pending task] (id 2.2) Progress: 2/4 tasks (50%)
The `[x]`/`[ ]` above is just the terminal rendering of each task's `done` flag — the source of truth is `window.PROJECT`, not a Markdown file.
If the active phase is still `roadmap-only` (not yet specced):
## Active Phase ### Phase [n]: [name] — roadmap-only Not specced yet. Run /own:feature to generate its spec, design & tasks.
If every phase is `complete`:
## Active Phase All phases complete 🎉 Run /own:feature to plan what's next.
---
Learning Stats (NEW)
## Learning Growth Patterns Documented: ███░░░░░░░ 4 Failures Documented: █░░░░░░░░░ 2 Total Insights: ████░░░░░░ 6 Domains Explored: • Auth: ████████░░ (8 learnings) • Forms: ████░░░░░░ (4 learnings) • API: ██░░░░░░░░ (2 learnings) • Database: ░░░░░░░░░░ (0 learnings) Current Level: ⭐⭐⭐ (Intermediate) Last Learning: "Always initialize array state as [] not undefined" (3 days ago)
Competency levels:
- ⭐ Beginner (0-5 learnings)
- ⭐⭐ Developing (6-15 learnings)
- ⭐⭐⭐ Intermediate (16-30 learnings)
- ⭐⭐⭐⭐ Advanced (31-50 learnings)
- ⭐⭐⭐⭐⭐ Expert (50+ learnings)
---
Recent Activity
## Recent Activity (Last 7 Days) Commits: - feat(auth): implement login form (2 days ago) - fix(api): resolve CORS issue (3 days ago) - chore(deps): update dependencies (5 days ago) Files Changed: 12 Lines Added: 342 Lines Removed: 89
---
Career Stats
**⚠️ Profile Check:** Read `.claude/ownyourcode-manifest.json` → `profile.settings.career_focus`
- If `"none"` → **SKIP THIS SECTION ENTIRELY**
- If `"full-extraction"` or `"tips-only"` → Show section below
## Career Portfolio Interview Stories: 3 - "Debugging race condition in form submission" - "Implementing JWT refresh rotation" - "Building accessible navigation" Resume Bullets: 3 - "Engineered secure authentication..." - "Resolved critical race condition..." - "Developed WCAG-compliant navigation..." Each feature you complete adds to your interview arsenal!
---
Step 3: Recommendations
Based on status, provide personalized recommendations:
If they have active work:
## Next Steps You're currently working on: [Feature Name] Current task: [Task description] Suggested action: Run /own:guide to continue implementing
If no active work:
## Next Steps Your roadmap shows these pending phases: - Phase 2: Core Features Suggested action: Run /own:feature to start your next feature
If they've been inactive:
## Welcome Back! It's been [X days] since your last commit. You were working on: [Feature] Want to pick up where you left off? Run /own:guide to continue, or /own:feature for something new.
If low learning stats:
## Learning Flywheel Reminder You have [X] learnings documented. Run /own:retro after completing tasks to capture insights. The more you document, the smarter /own:advise becomes!
---
Step 4: Visual Status
**Profile-Aware Visual:**
- Read `profile.settings.career_focus` from manifest
- If `"none"` → Omit CAREER STATS section from visual
Create a visual summary:
┌─────────────────────────────────────────────────────────────┐ │ PROJECT STATUS │ ├─────────────────────────────────────────────────────────────┤ │ Project: [Name]
Claude Code workflow for AI-mentored development. Work efficiently with Spec-Driven Development and the 6 Gates. Built to fight cognitive offloading — for developers using AI to grow and maintain ownership.
Repo: DanielPodolsky/ownyourcode
Other commands on ownyourcode.
- /advise
Pre-work command that queries past learnings and leverages MCPs before starting a new task
Open command - /docs
Guide the junior through writing documentation for their project or code
Open command - /done
Complete a task with 6 Gates verification, code review, and career value extraction
Open command - /feature
Create a feature specification using spec-driven development
Open command - /guide
Get implementation guidance for the current task
Open command - /init
Initialize OwnYourCode project with mission, stack, and roadmap
Open command

