Loading...
Loading...
Found 65 Skills
Initialize a long-running project with a structured docs workflow, or update an existing project (new features, bug fixes, refactors, requirement changes). Use this skill whenever the user wants to start a new project, kick off a long-running build task, set up project documentation structure, or says things like "new project", "start a project", "init project", "project setup", or "I want to build something from scratch". Also use when the user mentions wanting a milestone-based plan, structured execution workflow, or asks to scaffold documentation for a complex multi-step build. Additionally, use this skill when the user wants to modify an existing project that already has a `docs/` directory — e.g., "add a new feature", "fix this bug", "refactor X", "I want to change how Y works", "new feature request".
Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.
Creates a change proposal with clear intent, defined scope, and technical approach. Trigger: /sdd-propose <change-name>, create proposal, define change scope, sdd proposal.
Create or maintain STRATEGY.md - the product's target problem, approach, users, key metrics, and tracks of work. Use when starting a new product, updating direction, or when prompts like 'write our strategy', 'update the roadmap', 'what are we working on', or 'set up the strategy doc' come up. Also triggers when ce-ideate, ce-brainstorm, or ce-plan need upstream grounding and no strategy doc exists yet.
When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Write user-facing documentation for a new or changed feature, in the project's docs site. Use when user says 'document this feature', 'write user docs', 'create feature page', 'add to the docs site', or 'write the end-user guide'. Do NOT use for internal architecture docs (use arc42 or write-doc), ADRs (use document-decision), or CLAUDE.md updates (use create-or-audit-claude-md).
Add a new package to the Remotion monorepo, including package scaffolding, monorepo registration, documentation, build scripts, tests, and release checklist updates. Use when creating a new @remotion package.
Produces a standalone multi-page research dossier on the jackin' docs site from a brief, drawing on web and codebase evidence. Use when the operator runs /jackin-dev:research.
Guide for adding new AI provider documentation. Use when adding documentation for a new AI provider (like OpenAI, Anthropic, etc.), including usage docs, environment variables, Docker config, and image resources. Triggers on provider documentation tasks.
A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.
Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.