Stefan Teofanovic

Use when an agent orchestrates other agents on a piece of work, of any kind (a plan, a task swarm, a brainswarm): proposing a run tuned to the work, built on the closest protocol (build-verify, idea-to-outcome, brainstorm, debate, editorial, a project's own), settling it with the person, dispatching each member with its brief and role, watching them, judging their findings and steering a drift. Not for the duties one kind adds (orchestrate-plan for a plan, swarm for a task swarm, brainswarm for a seat swarm), and not for the board they talk on (swarm-board).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a person asks to swarm, delegate or parallelize work without a plan ('swarm this', 'run a swarm on…', 'get a few agents on it'), or when a task in front of you splits into independent parts or is long enough to hand off: then propose a swarm in one line, workers and why, and open it only on a yes. Runs a task swarm on the board: this session orchestrates, N swarm-worker agents take the tasks posted to them, report, and take the next, for as long as the person keeps giving work, on call or under a protocol (build-verify: builders, then verifiers walking the running product, looped until it holds). Produces the run on the board and the workers' results and merges. Not for work an approved plan covers (execute-plan), a discussion of seats (brainswarm), or a task small enough to do yourself.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a person wants to think an idea through and keep the discussion: a feature, a tool choice, an architecture question, before a plan or without one, with the agent through an interview. Produces a board in aiview holding the decisions, the diagrams and what was investigated. Not for a swarm of seats working it (brainswarm), not for an implementation plan and not for bug fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a person wants a swarm of role seats to work a topic on the swarm board under a chosen protocol: a brainstorm (ideas before any judgment), a debate (questions argued to decisions, a skeptic endorsing) or an editorial (one text drafted, read by seats standing for its readers, revised), a protocol or template the project keeps as a `protocol-<name>` skill (or an older `brainswarm-<name>` one), or a custom protocol recommended for the person's intent, or a seat's brief names a brainswarm protocol. Produces the run's record in aiview, written by the orchestrator alone. Not for one person thinking aloud with the agent (brainstorm, interview) and not for a plan's slices (execute-plan).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a person says "interview me" or asks to be interviewed about an idea or an existing design document (a board, a plan, a change) until it is understood the same way by them and the agent, or when another skill needs open decisions resolved one by one. Runs in chat and leaves the resolved decisions there, for the caller to write where they belong. Keeping the discussion as a document is brainstorm's, turning it into a plan is write-plan's.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a person wants to be questioned about a system they shipped, says "defend <feature>" or "whiteboard me on <subsystem>", or wants to be ready to explain and defend a design to anyone who pulls them aside. Hard questions on the system and on its stack, open-book. Produces a defense report: the gaps, the reading that closes them, and the architecture leads the questions turned up. Not a review of the code, not a test of the person, not a quiz on names and lines, and it changes nothing in the repository.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when code is hard to follow and is to be audited or reworked: long if/else or switch chains, cascades of type checks or parse attempts, kind fields compared to strings, flag parameters, deep nesting, a function hard to read. Also for complexity guardrails, or one long conditional function pasted. Produces a ranked audit of families, one family reworked behind characterization tests, or the guardrails.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a person asks to design a new module's interface or to rework an existing module so that it hides much behind little, in any tier (backend, frontend, test support, tooling), or says a module's callers know too much about it. Produces a module document in aiview, how a caller uses it, its one public entry point as signatures, what stays outside and the gap from today, discussed with the person until agreed. Not for writing the task that carries the rework out (orchestrate's tasks) and not for the rework itself.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a JavaScript or TypeScript project's dependencies must be seen as they are in the code: the whole graph, what one module depends on, who depends on it, or its neighbourhood, at file or folder level. Produces a Mermaid graph document in aiview, parsed by a deterministic script, never inferred. Not for designing a module's interface (deepen-module).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a document produced in this collection (board, plan, report, analysis, durable doc) could carry a diagram, or when a design question would settle faster shown than said. Picks the diagram that answers the open question and holds the discipline that keeps a diagram readable. Not for decoration: no open question, no diagram.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use whenever a document is produced for the user to read and react to while it evolves: a brainstorm board, a plan, a design language, a prototype, a PR analysis, a review report, a live PDF. Also when a document must be registered, opened, listed, moved or retired, or a prototype's bindings checked. Not for code, tests or configuration, or any file nobody opens in a browser.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when agents run together on the project's swarm board: a plan, a task swarm or a brainswarm, as its orchestrator or a member whose brief names a run, or when a run on the board has to be opened, read, interrupted or closed, or how the runs went has to be read from outside them. Produces nothing but the run's state on the board, or its figures. Not for documents (aiview).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when carrying out an implementation plan the person has already approved, whether starting it or resuming it in a later session, and the tracker in it has to stay true while the work happens. Not for producing the plan (write-plan) and not for reviewing the result.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use whenever execute-plan runs, as the plan's orchestrator: settling the mandate, running the plan phase by phase on the swarm board, dispatching the plan's workers once, posting each phase's tasks to them, watching the board, verifying merges, and handling the branch and pull request. Not for keeping the tracker or deciding when to pause (execute-plan), and not for doing a task (the swarm-worker agent).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when code is written or changed that branches heavily, in any language: if/else or switch chains, type-check cascades, kind fields compared to strings, flag parameters, deep nesting. Produces the branching shaped before it lands, and the bar it must meet at merge. Not for auditing or reworking existing code (complexity-rework).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a project needs a guide of its own: a rule for how a kind of code is shaped while written, scoped to the files it governs. Produces the project's `guide-<name>` skill at `<repo>/.claude/skills/guide-<name>/SKILL.md`. Not for a repository-wide convention (write-conventions) and not for a skill that does work (write-skills).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when code is written or changed that adds a module or changes a module's public interface, in any tier. Produces an interface shaped before the code behind it, and the bar it must meet at merge. Not for designing the interface with the person (deepen-module) and not for code that leaves every interface as it was.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use whenever the person needs to understand what is going on in this collection: they ask (how something works, what a term or a verb's answer means, what is happening in a run, what can be done here, how to start), they call help, or, unasked, the moment you notice they do not know or do not understand something of this ecosystem (a term they misuse or ask about, surprise at what a run or a skill does, a choice they cannot make for lack of the picture). Explains, in simple terms, what you are doing together and how this part of the landscape works, from the current work and its content, then guides them on. Not for running the skill it explains, and not for offering a skill unasked (next-step).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use at every point of a conversation where one of this collection's skills would serve the person better than going on as is, and they have not named it: an idea still vague or choices left open (offer the interview), decisions worth keeping (a brainstorm board), agreement on something to build (a plan, or a swarm with its protocol filled in), a question to decide or a text to write from several viewpoints (a brainswarm), a run that just closed (its follow-up). Produces one offer in one line; never runs the skill unasked. Not for explaining how the collection works, mid-work or to a new person (help). Not for running any of those skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when dispatched to cold-read a plan, as an agent that was not in the conversation that wrote it, to say whether it can be carried out from the document alone. Produces what the reader would build, its questions, and a verdict, ready or not ready, repeated as the writer fixes the plan. Not for judging the design (interview, pr-review), not for the mechanical checks (aiview plan check, tracker check), and not for writing the plan (write-plan).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when something non-trivial is to be built or reworked and its implementation plan has to be written, from an idea or from a board, or when a plan has to be redrawn after an increment landed. Produces, through an interview, the one plan document that holds the design, the decisions, the phases and seats, the tracker execute-plan runs from and the orchestrator's mandate. Not for keeping an open discussion (brainstorm), not for writing a phase's tasks (orchestrate-plan, at the phase's open) and not for carrying the plan out (execute-plan).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a project's leadership board opens and the project has no facilitator skill, or when a person asks for one or for the product's vision to be written down. Produces the project's `facilitator-<app>` skill (the vision, the principles and red lines the leadership board's facilitator rules by), drafted from the product as it is and settled through an interview. Not for running the board (the orchestrate skill's leadership board), the roadmap's slots (roadmap) or the project's code conventions (write-conventions).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a project has to be declared above its pieces of work, from nothing or from the boards, plans and prototypes already made, when a slot has landed or the picture has changed and the roadmap must be redrawn, or when someone asks where the project stands. Produces and keeps the roadmap (iterations of deliverable slots, each slot's state derived from what exists for it) and the foundation reference (the technology decisions). Not for designing a slot (brainstorm), planning it (write-plan) or building it (execute-plan).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the work produces a document that must be understood by someone who was not there when the system, procedure or decision was made, and that stays in the repository after the work merges: a README, an architecture or system document, an ADR, a runbook, an onboarding guide, an API guide, a migration note. Not for the working documents of a piece of work (boards, specs, plans and reports belong to the skills that produce them) and not for persuasive prose.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.