Showing 46201–46230 of 77200 skills
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
hancrafted/markdown-harness
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
hancrafted/markdown-harness
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
hancrafted/markdown-harness
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
hancrafted/markdown-harness
Writing, exploit: shape raw material into an article, paragraph by paragraph.
hancrafted/markdown-harness
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
hancrafted/markdown-harness
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
hancrafted/markdown-harness
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.
GravionLabs/elysion
Review a diff against acceptance criteria and language rules; blocking findings versus notes. Use for "review this code".
GravionLabs/elysion
Deliver a PBI, Bug, Feature or Epic item by item with subagents (implement, review, PR, CI, merge). Use for "/deliver 12" or "deliver feature 7".
GravionLabs/elysion
Diagnose bugs: red-capable feedback loop first, then minimal repro, ranked hypotheses, fix with regression test. Use for bug, fix, broken, failing, debug.
GravionLabs/elysion
GitHub issue conventions: types, [Level] titles, branches, commits, native sub-issues, plan-to-issue creation. Use for any GitHub issue work.
GravionLabs/elysion
Interview the user until no open decision is left. Use for "grill me", "ask me the open questions" or to answer a plan's questions[] or an issue's open decisions.
GravionLabs/elysion
Rules for code changes: every change ships with tests, dispatches to <lang>-implementation. Use for implement, write code, add feature, test requests.
GravionLabs/elysion
Build or modify Angular components with AG Grid Enterprise. Use when a task mentions ag-grid.
GravionLabs/elysion
Angular 21+ implementation and review rules (standalone, signals, DI, forms). Use when writing or changing Angular code.
GravionLabs/elysion
Plan an issue one level down with blockers and sizes, grill the open decisions, create the issues; refine <nr> checks readiness. Use for "plan issue #N" or "refine #N".
GravionLabs/elysion
Retrospective on a run or session: metrics, ranked environment improvements, draft PBIs and lessons. Use for "retro #<issue>" or "analyse this run"; creates no issue without approval.
GravionLabs/elysion
TypeScript implementation and test rules (Vitest) extending `implementation`. Use when writing or changing TypeScript or Node.js code.
GravionLabs/elysion
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.
GravionLabs/elysion
Review a diff against acceptance criteria and language rules; blocking findings versus notes. Use for "review this code".
GravionLabs/elysion
Deliver a PBI, Bug, Feature or Epic item by item with subagents (implement, review, PR, CI, merge). Use for "/deliver 12" or "deliver feature 7".
GravionLabs/elysion
Diagnose bugs: red-capable feedback loop first, then minimal repro, ranked hypotheses, fix with regression test. Use for bug, fix, broken, failing, debug.
GravionLabs/elysion
GitHub issue conventions: types, [Level] titles, branches, commits, native sub-issues, plan-to-issue creation. Use for any GitHub issue work.
GravionLabs/elysion
Interview the user until no open decision is left. Use for "grill me", "ask me the open questions" or to answer a plan's questions[] or an issue's open decisions.
GravionLabs/elysion
Rules for code changes: every change ships with tests, dispatches to <lang>-implementation. Use for implement, write code, add feature, test requests.
GravionLabs/elysion
Build or modify Angular components with AG Grid Enterprise. Use when a task mentions ag-grid.
GravionLabs/elysion
Angular 21+ implementation and review rules (standalone, signals, DI, forms). Use when writing or changing Angular code.
GravionLabs/elysion
Plan an issue one level down with blockers and sizes, grill the open decisions, create the issues; refine <nr> checks readiness. Use for "plan issue #N" or "refine #N".
GravionLabs/elysion
Retrospective on a run or session: metrics, ranked environment improvements, draft PBIs and lessons. Use for "retro #<issue>" or "analyse this run"; creates no issue without approval.
GravionLabs/elysion