From nx
Use when beads need enrichment with execution context, file paths, code patterns, constraints, and test commands. Audit findings incorporated when available.
npx claudepluginhub hellblazer/nexus --plugin nxThis skill uses the workspace's default tool permissions.
Delegates to the **plan-enricher** agent (sonnet). See [registry.yaml](../../registry.yaml).
Generates executable Markdown implementation plans for multi-step tasks from context briefs, resolving ambiguities, ordering dependencies, and enabling parallel worker execution.
Enhances existing plans by deploying parallel research agents per section to add best practices, optimizations, UI/UX improvements, edge cases, and real-world examples.
Share bugs, ideas, or general feedback.
Delegates to the plan-enricher agent (sonnet). See registry.yaml.
/nx:enrich-planUse the Agent tool to invoke plan-enricher:
## Relay: plan-enricher
**Task**: Enrich all beads with execution context and codebase alignment
**Bead**: [epic bead ID] or 'none'
### Input Artifacts
- nx scratch: plan structure, bead IDs, audit findings (if present from same-session /nx:plan-audit)
- Files: [RDR file path if known]
### Deliverable
All beads enriched with file paths, code patterns, test commands, dependency constraints, and (when available) audit gap mitigations. Epic bead ID persisted to T2.
### Quality Criteria
- [ ] Every bead enriched with execution context
- [ ] Epic bead ID written to T2 for close-time advisory
- [ ] Enrichment summary reported to user
For full relay structure and optional fields, see RELAY_TEMPLATE.md.
T1 scratch is session-scoped. When invoked after /nx:plan-audit in the same session, audit findings from T1 are automatically incorporated. Standalone invocation works without audit findings — codebase-derived context is the primary enrichment value.
/beads:update <id> --body-file /tmp/bead-<id>.md with execution-ready context