FelipeCarillo

holoctl-foreign-bootstrap

Use when you are an AI coding assistant that is NOT Claude Code, operating in a repo that contains a `.holoctl/` directory (or whose `AGENTS.md` points here). holoctl natively materializes only Claude Code's config (`.claude/` + `CLAUDE.md`); this skill teaches any other assistant (Copilot, Codex, Cursor, Aider, Zed, Windsurf, …) to read the canonical source in `.holoctl/` and generate its OWN native config dir from it.

holoctl-parallel-evaluator

Use when the user describes work that touches multiple files or modules, BEFORE committing to a single-ticket creation. Evaluates parallelization potential and proposes a batch decomposition if independent file sets exist. Hands the candidate decomposition to the boardmaster.

holoctl-persona-suggester

Use when the user describes work, or recent file edits touch paths, that aren't owned by any active persona. Detects emerging specialization signals (a new file type appearing repeatedly, a directory pattern unique to a specialty, a request mentioning a domain outside boardmaster/developer/ reviewer/architect/researcher scope) and surfaces a suggestion: either activate an existing library persona, or invoke /agent-new to design a brand-new persona tailored to this project.

holoctl-provider-mcp

Use when the user pastes a URL from an external board (Linear, GitHub, Trello, Azure DevOps, Jira, Slack, or a custom internal board) or refs a card by id. Detects the provider via configured URL patterns, probes whether the provider's MCP tool is connected in Claude Code, and either fetches the card body via that MCP or falls back to asking for paste. Pre-fills source_* fields on the resulting work item.

holoctl-router

Use when the user types `/holoctl`, mentions "holoctl"/"hctl", asks for project status / what's pending / what's next, asks to create a ticket or close a session, or operates in a directory that looks like a holoctl workspace but the assistant isn't sure of its state. Detects workspace state via `hctl doctor` and routes to the right flow.

holoctl-spec-flow

Use when the user pastes content from an external board (Trello/Linear/ Azure DevOps/Jira/GitHub/Slack), or shares a multi-paragraph request that needs structuring before coding. Drives the Spec-Driven Development flow: intake → materialize early → live authoring → review → decompose → execute. The spec ticket body is a live plan document the user watches in the dashboard while the discussion happens in chat. Companion to the `/spec` slash command and the `holoctl-work-item-router` skill.

holoctl-ticket-discipline

Use when the user announces non-trivial work (refactor, feature, bugfix, improvement) and no ticket has been created for it yet. Checks if a ticket already exists; if not, suggests creating one (or a parallel batch) before implementation starts. Tracks work that would otherwise vanish.

holoctl-work-item-router

Use when the user describes work to be tracked and the work kind isn't obvious. Infers whether it's a task, story, bug, spec, epic, or incident from the language used, then routes to the right entry point (`/ticket`, `/spec`, or direct boardmaster call) with the correct `kind` pre-set.

holoctl-memory-discipline

Use when the user makes a durable decision, states a project rule, or shares context that future sessions will need ("vamos sempre X", "decidi Y", "lembra que Z"). Promotes the right material to the right surface: ADR for hard locks, memory topic for soft durable context.