메뉴
SkillsMP는 azure-id/orc에서 39개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
수집된 skill 39개 중 39개를 표시합니다.
Did the thing we shipped hold up. Use for "/orc-aftermath", "did that change stick", "what did we ship last month and how did it go", "which runs came back". Read-only and report-only: it grades past runs from the repository's own future — files rewritten…
원문 언어: 영어
System Analyst for ORC. Use for "/orc-analyze", "analyze this doc for scope X", or "analyze this requirement against the code" — turning a requirement (a document, PDF by path or pasted, OR a plain-language request) into a precise, code-grounded requirement…
원문 언어: 영어
The lane that says what an agent should NOT try here, and why. Use for "/orc-boundary", "should the agent even attempt this", "where does automation stop in this repo", "why did ORC refuse that". Three verdicts per AREA — EXECUTE, ESCALATE, REFUSE — each…
원문 언어: 영어
Standalone idea-generation lane — arrive with a problem, a goal, or a hunch and leave with ONE chosen direction plus every rejected direction written down with the reason it lost. Use for "/orc-brainstorm", "I don't know what to do about X", "give me…
원문 언어: 영어
What a run will cost, in the unit YOU are billed in. Use for "/orc-budget", "what will this plan cost", "which lane is cheaper here", "how much did that run burn", "will this hit my limit". Given a PLAN — not a sentence — it forecasts a token vector (fresh…
원문 언어: 영어
Grade a FINISHED artifact — a TSD, a PRD, an ADR, an API contract, a README, a runbook, a plan, or a module of code — against a goal YOU state, then stop and make you go and fix it somewhere else. Use for "/orc-challenge", "review my TSD", "is this document…
원문 언어: 영어
CLAUDE.md builder/updater for the LOCAL project. Use for "/orc-claude", "build a CLAUDE.md", "update the CLAUDE.md", or "refresh the CLAUDE.md". Runs INDEPENDENTLY — no orchestrator, no run folder. Scans the repo for ground-truth facts (verified commands,…
원문 언어: 영어
User-composable ORC lane. Use for "/orc-diy" or "run my custom orc flow". The pipeline shape (analyze/review/verify/security/testgen on-off, scoring or a fixed executor, autonomy, ship mode, session tier) is configured ENTIRELY through the `orc diy` CLI and…
원문 언어: 영어
Write a long document — a PRD, a TSD, a cross-team collaboration agreement, a status report or a workflow/runbook — as portable Markdown that imports cleanly into Notion, Obsidian, Google Docs, Coda, Craft and GitHub. Use for "/orc-doc", "write the PRD for…
원문 언어: 영어
Say it again, so it lands. Use for "/orc-explain", "wait, what?", "I did not follow that", "explain that again". The user has just read something from ORC they did not understand — a preflight block, a scoring line, a gate result, a question. Re-pitch that…
원문 언어: 영어
The portability lane. Use for "/orc-export", "export our context to AGENTS.md", "are we locked into ORC", "make this readable by Cursor/Codex", "import our existing AGENTS.md". OUT compiles the wiki, orientation doc, code patterns, PACT.md and boundary cards…
원문 언어: 영어
Fastest ORC lane — knowledge-gated single-executor implementation. Use for "use orc-fast to implement X" or "/orc-fast". Requires TWO prerequisites: a fresh project wiki (orc-wiki) AND a cached code-pattern for the request's language — the precomputed…
원문 언어: 영어
Standalone idea-sharpening lane — start from one vague sentence and leave with a settled idea written down. Use for "/orc-grill", "help me think this through", "I want X but I do not know what I want yet", "something is wrong with Y". It asks you rounds of…
원문 언어: 영어
Per-feature onboarding docs for the LOCAL project. Use for "/orc-learn", "help me learn feature X", "onboard me to this feature", or "orc-learn refresh". Runs INDEPENDENTLY — no orchestrator, no run folder. Picks one feature (wiki topics first), then…
원문 언어: 영어
Lightweight ORC for fast implementation. Use for "use orc-mini to implement X" or "/orc-mini". Same intake → intent-spec → planning → dispatch → smoke-gate → ship spine as the full orchestrator, but SKIPS full code review, verification, and the summary phase.…
원문 언어: 영어
The invariant ledger — the promises your system makes, and which ones are in doubt right now. Use for "/orc-pact", "what did we decide about X", "is that still true", "record this as a rule", "what are our invariants". It harvests the constraints /orc-grill…
원문 언어: 영어
Learn and cache a project's real code conventions per language so ORC executors write code that MATCHES the existing codebase instead of a generic template. Use for "/orc-pattern", "learn my code pattern", "codify conventions", or when ORC detects…
원문 언어: 영어
Poly-repo planning lane — plan ONE change that spans two or more repos (BE endpoint + FE UI, service + its gRPC consumer, etc.) without drift. Use for "/orc-poly", "plan this across both repos", "coordinate a change over these repos". Runs in the HOST repo…
원문 언어: 영어
Standalone quick lane — ask for anything, get it done in few steps. Use for "/orc-quick", "quick fix X", "quickly find out how Y works", "fix the review comments on PR N". Not only for code: a fast context dig, a defect hunt, a dependency bump, or a PR…
원문 언어: 영어
Retro miner for ORC — closes the behavior-trace flywheel. Use for "/orc-retro", "analyze the orc traces", "how well is orc scoring", or "what should we tune from the logged runs". Reads the persistent behavior traces in log_dir (behavior-trace logging is…
원문 언어: 영어
Plan-only lane router — you have a plan, this tells you which lane should build it. Use for "/orc-route", "which lane for this plan?", "is this worth the full orc run?". It reads the plan's own numbers (tasks, waves, files, top score, risk) plus ORC's…
원문 언어: 영어
Use when orchestrating a multi-task build through a full pipeline: intake → planning → scored parallel execution → review → verify → ship. Triggers: "orchestrate this", "build this in parallel", "run this with subagents", "use orc", or any request to take a…
원문 언어: 영어
Standalone verification for ORC. Use for "verify my changes", "/orc-verify", or "check the modified files". Runs INDEPENDENTLY — no orchestrator, no planning, no run folder required. Verifies only the git-modified changes in the working tree and shows a…
원문 언어: 영어
Wait for wall-clock time to pass without losing the run you are in. Use for "/orc-wait", "/orc-wait 30", "/orc-wait 2h hard", "wait for my quota to reset", "pause this until the window resets". You watched the statusline, you saw the window was almost full,…
원문 언어: 영어
Build and maintain a persistent project knowledge base for ORC. Use for "/orc-wiki", "build the project wiki", "scan the codebase for a knowledge base". Scans the project with Opus 4.8 high and writes wiki/orc-feature-*, wiki/orc-reference-*, and…
원문 언어: 영어
Combines 2+ RELATED, already-confirmed ORC analyses (from orc-analyze) into ONE merged, deduped, conflict-resolved requirement context before build. Use when the user analyzed multiple related documents within the same scope and chose "pass to…
원문 언어: 영어
Fast-lane System Analyst for ORC-MINI (Sonnet 5, high effort). Turns a requirement — a document (PDF by path or pasted) OR a plain-language request — into a scope-bounded, code-grounded requirement report + derived spec: bounds the deliverable to exactly the…
원문 언어: 영어
The lane for people who do not read code. Use for "/orc-handoff", "I want to change the text on the empty cart page", "can I edit this myself", "what can a PM safely change here". Two modes. MAP finds the files a non-engineer can own — screen text, content,…
원문 언어: 영어
Stacked-PR DRIVER. Use for "/orc-pr-driver", "build the stacked PRs", "submit the stack", "restack / sync / merge my stack". Takes an approved stacked-pr/<slug>/stack-plan.md — written by /orc-pr-setup, generated by `orc pr stack template` and filled in by…
원문 언어: 영어
Stacked-PR PLANNER. Use for "/orc-pr-setup", "plan the stacked PRs", "split this change into stacked pull requests", "where do the PR cut lines go". Decides the LAYERING of a big change — ordered layers, each with a purpose, a value class, an explicit file…
원문 언어: 영어
Requirement Planner for ORC (Opus 5 medium). Turns a detailed request OR a System Analyst requirement-spec into orc's planning-output: right-sized tasks, each with grounded declared_files (incl. tests), explicit depends_on, owns_area, and spec_ref —…
원문 언어: 영어
Ship-phase subskill for ORC Phase 8. Handles commit, push, and PR file generation from the team's template (pr.md in this folder). Coordination skill: always runs inline. Not for direct user invocation.
원문 언어: 영어
Executor worker for ORC — the single-task implementer. Given one task slice (task_id, declared_files, constraints, spec_ref, log_digest), it implements EXACTLY that task within its declared files, honors every hard-rule constraint, creates/updates tests,…
원문 언어: 영어
Review/verify worker for ORC Phases 5–6 (Opus 5 medium). Two modes: a REVIEW pass — examine the changed files against the code pattern + constraints, create/update tests, and classify EVERY finding on the P0–P3 severity ladder (P0/P1 gate ship, P2/P3…
원문 언어: 영어
Pre-analysis Advisor for the ORC ultra lane. Runs ONCE at ultra Phase U0 (after intake, before the analyst) to produce a code-grounded advisory brief: domain risks, alternatives, a mandatory security-risk section, a request-specific rubric the ultra judges…
원문 언어: 영어
Judgment gates for the ORC ultra lane. One judge skill, one agent (orc-judge-opus-5-xhigh), three dispatch contexts: gate=analysis (after the analyst), gate=plan (after the planner), gate=implementation (after verify — the anti-miss-implementation fidelity +…
원문 언어: 영어
Fast-lane Requirement Planner for ORC-MINI (Sonnet 5, high effort). Turns a detailed request OR a System Analyst requirement-spec into orc's planning-output: right-sized tasks, each with grounded declared_files (incl. tests), explicit depends_on, owns_area,…
원문 언어: 영어
Worker subskill for ORC's opt-in Phase 6.5 (Test Authoring). Fires when the user opts into writing tests ("write test cases", "generate tests", "author test cases for these changes"). Writes test cases as a deliverable — automated test files, a manual…
원문 언어: 영어
Stateless persistence service for ORC — the checkpoint read/write engine. On a trigger passed in by the orchestrator (batch_pause | token_limit | phase_transition | crash_guard), it atomically writes run/{slug}/checkpoint.json, regenerates the 10-line…
원문 언어: 영어