work
- Repo stars 330
- License MIT
- Author repo claude-skill-registry
- Domain
- Data
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Pick Up Work
Find and start work on an expedition. If an expedition ID is provided ($ARGUMENTS), start that one. Otherwise, find the next highest-priority ready item.
## Steps
### 1. Check Current Work
First, check if already working on something:
```bash
yurtle-kanban list --status in_progress
```
If items are in progress, show them and ask if the user wants to continue or pick up new work.
### 2. Find Ready Work
If no specific expedition requested:
```bash
yurtle-kanban list --status ready --limit 5
```
Show the top 5 ready items with their priorities.
### 3. Start Work
Once an expedition is selected (either from $ARGUMENTS or user choice):
```bash
# Move to in_progress
yurtle-kanban move EXP-XXX in_progress
# Create expedition branch from main
git checkout main
git pull origin main
git checkout -b expedition/exp-XXX-short-description
```
**IMPORTANT**: Expedition branches use the `expedition/exp-XXX-name` prefix and are never deleted (permanent memory).
### 4. Load Context
Read the expedition file to understand the work:
```bash
# Find and read the expedition file
cat kanban-work/expeditions/EXP-XXX*.md
```
Summarize:
- What needs to be done (Build Steps)
- Success criteria
- Dependencies
- Current status from Ship's Log
### 5. Ready to Work
Confirm the expedition is loaded and ready to begin implementation.
Sections and files
Listed in source order.
sections -> Steps → 1. Check Current Work → 2. Find Ready Work → 3. Start Work → 4. Load Context → 5. Ready to Work
terms -> IMPORTANT · Find and start work on an expedition. · If items are in progress, show them and ask if the user wants to continue or pick up new work. · Show the top 5 ready items with their priorities. · IMPORTANT: Expedition branches use the expedition/exp-XXX-name prefix and are never deleted (permanent memory). · Confirm the expedition is loaded and ready to begin implementation.
files/cmd -> expedition/exp-XXX-name · expedition/exp-XXX-short-description · kanban-work/expeditions/EXP-XXX
body sha256 -> b49c31261ea3
1. Check Current Work
First, check if already working on something: If items are in progress, show them and ask if the user wants to continue or pick up new work.
2. Find Ready Work
If no specific expedition requested: Show the top 5 ready items with their priorities.
3. Start Work
Once an expedition is selected (either from $ARGUMENTS or user choice): IMPORTANT: Expedition branches use the
expedition/exp-XXX-nameprefix and are never deleted (permanent memory).4. Load Context
Read the expedition file to understand the work: Summarize: What needs to be done (Build Steps) Success criteria Dependencies
5. Ready to Work
Confirm the expedition is loaded and ready to begin implementation.