project
/project
Show detailed status of a specific project by reading its archive, project_plan, and issues. Use for deep dive into one project's state.
- Author
- varie-ai ↗
- Repository
- workstation ↗
- Licence
- MIT
- Last repository change
- 24.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Show detailed status of a specific project by reading its archive, project_plan, and issues. Use for deep dive into one project's state.
Original author description
Show detailed status of a specific project by reading its archive, project_plan, and issues. Use for deep dive into one project's state.
How it works
- When to Use
- Arguments
- Implementation
- If Project Not Found
- If No Archive/Project Structure
- Example
SKILL.md preview
---
name: project
description: Show detailed status of a specific project by reading its archive, project_plan, and issues. Use for deep dive into one project's state.
arguments: "<project-name>"
---
# /project <name>
Show detailed status of a specific project.
## When to Use
- Deep dive into one project's current state
- Before resuming work on a project
- Preparing standup/status for a specific project
- Understanding what was done and what's pending
## Arguments
`<project-name>` - Name or alias of the project (as defined in projects.yaml)
## Implementation
### 1. Resolve project repos
```bash
# Read from projects.yaml
cat ~/.varie/manager/projects.yaml
# Find project by name or alias
# Get repos array (single or multiple)
```
Project can have one or more repos:
```yaml
# Single repo
webapp:
repos:
- path: /path/to/webapp
# Multi-repo
platform:
repos:
- path: /path/to/backend
role: api
- path: /path/to/frontend
role: web
```
If project not found, suggest adding to projects.yaml.
### 2. Read project structure (for each repo)
Check what exists in each repo:
```bash
# Check for archive/
ls <repo>/archive/ 2>/dev/null
# Check for project_plan/
ls <repo>/project_plan/ 2>/dev/null
# Check for issues/
ls <repo>/issues/ 2>/dev/null
# Check for CLAUDE.md
cat <repo>/CLAUDE.md 2>/dev/null | head -50
```
### 3. Read latest archive entry
```bash
# Find most recent feature
LATEST=$(ls -t <repo>/archive/ | head -1)
# Read HANDOVER.md
cat <repo>/archive/$LATEST/HANDOVER.md
# Read TODO.md
cat <repo>/archive/$LATEST/TODO.md
```
### 4. Read project plan index
```bash
cat <repo>/project_plan/INDEX.md 2>/dev/null
```
### 5. Read issues index
```bash
cat <repo>/issues/INDEX.md 2>/dev/null
```
### 6. Format output
```
# Project: webapp
**Path:** ~/projects/webapp
**Status:** Active session (ml2abc123)
---
## Current Work
**Feature:** 03_user_auth
**Status:** Step 3/5 - frontend_api_client (in_progress)
### Recent Progress
- Backend implementation complete
- API contract updated
- Working on frontend types
### Next Steps
1. Complete response type definitions
2. Update React components
3. Integration testing
---
## Project Plan
| ID | Feature | Status |
|----|---------|--------|
| P01 | User Auth | Complete |
| P02 | Dashboard | Complete |
| P03 | API Integration | In Progress |
| P04 | Mobile Support | Planning |
---
## Open Issues
| ID | Issue | Priority | Status |
|----|-------|----------|--------|
| 005 | Session timeout bug | P1 | Open |
| 007 | Dark mode flickering | P2 | Open |
---
## Quick Actions
- /route webapp "continue work" - Resume this project
- /dispatch ml2abc123 /work-status - Get live status
```
## If Project Not Found
```
Project "foo" not found.
Registered projects:
- webapp
- varie
- data-pipeline
Add a new project to ~/.varie/manager/projects.yaml:
```yaml
projects:
foo:
path: /path/to/foo
status: active
```
```
## If No Archive/Project Structure
```
# Project: my_project
**Path:** /path/to/repo
**Status:** No active session
No archive/ or project_plan/ structure found.
This project doesn't use the Varie workflow structure yet.
To start tracking:
1. Create archive/ directory
2. Use /work-start to begin tracked work
```
## Example
**User:** `/project webapp`
Shows full status including current feature, recent progress, project plan, and open issues.
**User:** `/project character` (using alias)
Resolves alias from projects.yaml, shows same detail.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · varie-ai/workstation | 100 | MIT |
| LandonSchropp/agent-toolkit | 100 | MIT |
| stefanocaronia/claude-project | 100 | MIT |
| erayozenn/BigHead-2ndBrain | 100 | MIT |
| adivmaimon/Caddis | 100 | MIT |
| samchon/typia | 100 | MIT |
| systemfsoftware/systemfsoftware | 100 | Apache-2.0 |
| systemfsoftware/systemfsoftware | 100 | Apache-2.0 |
| kriegcloud/beep-beginners | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 5aef791d2e80 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90status
Show the progress board of specs in specs/ and what to work on next, or the detailed state of one spec. Use when asked about progress, status, or what to do next. - 100project-overview
Use when the user asks about a specific project or all projects — e.g. 'show me project X', 'project overview', 'what projects do I have', 'project summary - 100complete-project
This skill should be used when the user asks to 'complete a project', 'wrap up a project', 'archive a project', or 'run project completion'. - 95tl-status
Graph-aware project status with SA coverage metrics. Reads Task/Wave nodes from Neo4j, falls back to status.json.Use when: project status with graph, check progress with SA coverage, or the user says "/nacl:tl-status". - 100project-dashboard
This skill should be used when users ask 'where am I?', 'what is my progress?', mentions 'status', 'dashboard', 'progress', wants to know if they are ready for the next stage, or needs an overview of their project state. - 100apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.