All authors
Claude Skills by hectorcanaimero
github.com/hectorcanaimero9 skills0 installs12 views
- Orch ArchUse when an accepted PRD under docs/prd/ needs a technical architecture before specs are written (step 2 of orch-plan). Reads the code and the PRD, writes docs/arch/NNN-<slug>.md with components, contracts, decisions and the phase/package split orch-spec turns into tasks. Never writes code, specs or tasks.json.Votes: 0GitHub stars: 2
- Orch PlanUse when the user describes a feature or product idea and wants it planned end to end for orch ("plan this", "/orch-plan <idea>"). Drives the pipeline PRD → ARCH → SPEC → TASKS through orch-prd, orch-arch, orch-spec and orch-tasks, stopping for the user at each gate and resuming from whatever artifact already exists.Votes: 0GitHub stars: 2
- Orch PrdUse when the user wants to turn a product or feature idea into a PRD for an orch-managed project (step 1 of orch-plan). Interviews for the missing facts, then writes docs/prd/NNN-<slug>.md with numbered, testable requirements that orch-arch and orch-spec can trace. Never writes code, specs or tasks.json.Votes: 0GitHub stars: 2
- Orch SpecUse when an architecture under docs/arch/ needs to become dispatchable work for orch (step 3 of orch-plan). Writes specs/fN-<slug>.md in the exact markdown format orch atomize parses — phase, package and task headers with Model, Estimate, Reason, Dependencies and Files — one agent-sized task per header. Never edits tasks.json.Votes: 0GitHub stars: 2
- Orch TasksUse when specs under specs/ are ready to become tasks in an orch project (step 4 of orch-plan, or on its own after editing a spec). Runs orch atomize as a dry-run, shows the diff, applies it only after the user confirms, then makes the DAG valid with orch router and orch validate and explains how to promote tasks out of backlog.Votes: 0GitHub stars: 2
- OrchUse when the user's cwd contains .orchestrator/ or tasks.json (a project managed by the orch CLI). Explains the task DAG model, where runtime state lives (SQLite), how to inspect it without editing tasks.json, how to legally move a task between states, and which commands are safe from an agent session. Load on demand — no need to keep in system prompt.Votes: 0GitHub stars: 2
- Orch DiscoverUse before planning on a repository that already has code (step 0 of orch-plan, or alone when you inherit a codebase). Reads the code, configs and CI, and writes docs/arch/000-discovery.md with evidence-backed facts, gaps, boot-time side effects and questions for the client, then proposes orch config and rules the operator confirms. Never writes code, specs or tasks.json.Votes: 0GitHub stars: 2
- Orch E2eUse when an orch task asks for end-to-end tests of a web app (an E2E task, usually the last of a phase, writing tests/e2e/*.spec.ts). Bring the app up, explore it in a real browser through its accessibility tree, and write Playwright specs with role-based locators that fail when a user-visible behaviour breaks — then run them against the app until they pass.Votes: 0GitHub stars: 2
- Orch TddUse when implementing an orch task test-first (dispatch.tdd on, or a task whose Done when lists tests). One failing test per acceptance criterion, seen failing for the right reason, then the least code that makes it pass, then cleanup — with the repository's own test framework — and a done note that names the tests.Votes: 0GitHub stars: 2