Skip to content

afx skill missing workspace recover / add-architect / remove-architect subcommands #889

@amrmelsayed

Description

@amrmelsayed

Problem

The afx skill bundled in the skeleton (codev-skeleton/.claude/skills/afx/SKILL.md and packages/codev/skeleton/.claude/skills/afx/SKILL.md) documents afx workspace start and afx workspace stop but omits three subcommands that afx workspace --help actually exposes:

  • afx workspace recover — revive builders whose shellper died (e.g. after a machine reboot). Has flags --apply, --max-age <days>, --include-stale, -y, --yes.
  • afx workspace add-architect — add a named sibling architect terminal to the active workspace.
  • afx workspace remove-architect <name> — remove a sibling architect (cannot remove main).

Impact

Agents loading the skill to answer questions about post-reboot recovery don't know afx workspace recover exists and fall back to telling users to loop afx spawn <id> --resume per builder — strictly worse UX than the purpose-built command. Same gap blocks discovery of sibling-architect setup, even though the multi-architect feature is documented elsewhere in CLAUDE.md.

Reproduction

grep -n -A6 "^## afx workspace" codev-skeleton/.claude/skills/afx/SKILL.md
# Shows only start / stop, no recover / add-architect / remove-architect.

afx workspace --help
# Lists start, stop, add-architect, remove-architect, recover.

Fix

Extend the ## afx workspace section in both skeleton copies (codev-skeleton/.claude/skills/afx/SKILL.md and packages/codev/skeleton/.claude/skills/afx/SKILL.md — they should stay in sync) to document the three missing subcommands with their flags, mirroring the level of detail already present for afx spawn and afx cleanup. afx workspace recover in particular should explicitly call out the machine-reboot use case so it surfaces when agents are asked about recovery.

Metadata

Metadata

Assignees

Labels

area/coreArea: shared core library / forge abstraction (packages/core, packages/codev/src/lib)

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions