Loading...
Loading...
Found 9,894 Skills
Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.
Fact-checks OpenSpec user documentation with a fresh-context subagent that re-runs commands and checks claims against source. Manually triggered; not part of the drafting loop. Use when the user asks to verify, fact-check, or accuracy-check a docs page, section, or set of changed claims.
Fan out independent read and write lanes.
Assemble the per-PR changeset entries in docs/content/changelog/upcoming/ into a release's changeset-0-XX.md and generate the detailed CHANGELOG.md sections. Use at release time when the user wants to build or finalize the changelog or changeset for a Rerun release, or merge the upcoming/ entries. Invoked via /assemble-changelog or "assemble the changelog for 0.x.y".
Route finance questions to an existing local script, a new You.com Finance Research API call, or an MCP payment-aware fallback.
Turn a settled business-logic spec (from `feature-discovery` or a freshly-described feature in chat) into a detailed, code-grounded implementation plan saved as `docs/<feature-slug>-plan.md`, ready for `plan-task-breakdown` to convert into checkboxes. Verifies feasibility against the actual codebase, names the specific files/types/actions/components to touch, identifies test cases at every layer that fits (unit, integration, and — for user-visible flows — a Playwright happy-path e2e test), and asks the user clarifying questions for implementation-level ambiguities only — never re-litigates business logic. Use this skill whenever a feature's *what* is clear and the next move is mapping it to *how*. Trigger on phrases like "make a plan", "write the implementation plan", "plan this out", "design the build", "turn this spec into a plan", "how would we implement this", "scope out how to build X", "draft a plan for <feature>", or whenever the conversation just produced a business spec and the natural next step is implementation design — even if the user doesn't say "implementation plan" explicitly.