blocked

Data Community

Repo stars 330
License MIT
Author repo claude-skill-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Mark expedition as blocked with reason and optional unblock agent Mark an expedition as blocked with a clear reason so other age…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Required Arguments”, “Optional Arguments”, “Steps”, “1. Move to Blocked Status”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name blocked directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Required Arguments / Optional Arguments / Steps” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Mark as Blocked

Mark an expedition as blocked with a clear reason so other agents know why and who can help.

Required Arguments

EXP-XXX - The expedition ID to block
reason - Why it's blocked (quote if multiple words)

Optional Arguments

--unblock-by agent-X - Which agent can unblock this

Steps

1. Move to Blocked Status

yurtle-kanban move EXP-XXX blocked

2. Update Expedition File

Add a blocked section to the expedition file:

Find the expedition file and add after the frontmatter:

> **BLOCKED**: [reason]
> **Since:** YYYY-MM-DD
> **Can unblock:** [agent-X or "anyone"]

Also add a Ship's Log entry:

### YYYY-MM-DD: BLOCKED

**Reason:** [reason]
**Can unblock:** [who]
**Context:** [any additional context]

3. Commit and Push

git add kanban-work/expeditions/EXP-XXX*.md
git commit -m "blocked(exp-XXX): [short reason]

Co-Authored-By: Claude <noreply@anthropic.com>"
git push origin HEAD

4. Confirm Block

Show:

Current blocked items count
Who can unblock
Suggest notifying the unblocking agent

Common Block Reasons

Reason	Who Can Unblock
"Waiting for GPU training to complete"	agent-a, agent-c
"Needs architecture decision"	agent-b, agent-d, captain
"Waiting for PR review"	any agent
"Blocked by EXP-XXX"	whoever finishes that expedition
"Needs Captain input"	captain
"External dependency"	depends

Unblocking

When you unblock an item:

Remove the > **BLOCKED** section from the file
Add Ship's Log entry: "Unblocked: [what changed]"
Move status: yurtle-kanban move EXP-XXX in_progress

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: 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
Author / version / license: @majiayu000 · MIT
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview blocked.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Mark as Blocked

Mark an expedition as blocked with a clear reason so other agents know why and who can help.

## Required Arguments

- `EXP-XXX` - The expedition ID to block
- `reason` - Why it's blocked (quote if multiple words)

## Optional Arguments

- `--unblock-by agent-X` - Which agent can unblock this

## Steps

### 1. Move to Blocked Status

```bash
yurtle-kanban move EXP-XXX blocked
```

### 2. Update Expedition File

Add a blocked section to the expedition file:

Find the expedition file and add after the frontmatter:

```markdown
> **BLOCKED**: [reason]
> **Since:** YYYY-MM-DD
> **Can unblock:** [agent-X or "anyone"]
```

Also add a Ship's Log entry:

```markdown
### YYYY-MM-DD: BLOCKED

**Reason:** [reason]
**Can unblock:** [who]
**Context:** [any additional context]
```

### 3. Commit and Push

```bash
git add kanban-work/expeditions/EXP-XXX*.md
git commit -m "blocked(exp-XXX): [short reason]

Co-Authored-By: Claude <noreply@anthropic.com>"
git push origin HEAD
```

### 4. Confirm Block

Show:
- Current blocked items count
- Who can unblock
- Suggest notifying the unblocking agent

## Common Block Reasons

| Reason | Who Can Unblock |
|--------|-----------------|
| "Waiting for GPU training to complete" | agent-a, agent-c |
| "Needs architecture decision" | agent-b, agent-d, captain |
| "Waiting for PR review" | any agent |
| "Blocked by EXP-XXX" | whoever finishes that expedition |
| "Needs Captain input" | captain |
| "External dependency" | depends |

## Unblocking

When you unblock an item:

1. Remove the `> **BLOCKED**` section from the file
2. Add Ship's Log entry: "Unblocked: [what changed]"
3. Move status: `yurtle-kanban move EXP-XXX in_progress`

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Required Arguments → Optional Arguments → Steps → 1. Move to Blocked Status → 2. Update Expedition File → YYYY-MM-DD: BLOCKED
terms    -> BLOCKED · Since · Can unblock · Reason · Context
files/cmd -> EXP-XXX · reason · --unblock-by agent-X · > BLOCKED · yurtle-kanban move EXP-XXX inprogress
body sha256 -> f0d38ba13473