Loading...
Loading...
Found 306 Skills
Bootstrap a Memory Bank for a new or existing repository, then route into PRD-driven or brownfield workflows.
Product requirements → living doc Requirements section + quality gate + domain glossary. Stateful: detects existing sections and resumes where needed. Triggers: 'define this,' 'write a PRD,' 'define requirements,' 'spec this out,' post-explore. Not for: scoping (explore), UX (design), technical design (architect).
Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear implementation brief. Triggers on I want to add, we should build, can we make, what is the plan for, how do we implement, dev brief, feature spec, PRD, user story, acceptance criteria, scope this, prioritize. Also triggers when the user has a list of things they want to build and needs help converting them into well-formed tasks.
Produces a compact briefing document for an AFK agent taking on a specific slice. Use after create-prd or create-issues, immediately before handing work to a coding agent. Do NOT interview the user — synthesise from the current context.
Save progress and generate a continuation prompt. Updates PRD status markers, captures git state, and writes checkpoint.md for the next session.
Analyze a PRD for edge cases, failure modes, and scenarios that might be missed. Use after creating a PRD to strengthen it. Triggers on: analyze edge cases, find edge cases, what could go wrong, edge case analysis.
Unified prompt engineering and requirements planning. Use when exploring ideas, improving prompts, creating PRDs, generating task breakdowns, or iterating on existing plans. Includes Jira integration for creating subtasks from plans.
Comprehensive content review and quality assurance for EARS documents - validates requirement syntax, PRD alignment, testability, and identifies issues requiring manual attention
Generate social media content pack from PRD — LinkedIn post, Reddit answer draft, and Twitter/X thread. Use when user says "create content", "write LinkedIn post", "social media pack", "marketing copy", or "promotion content". Do NOT use for community thread responses (use /community-outreach) or video scripts (use /video-promo).
Generate clickable HTML wireframes for every screen in the PRD. No design tool needed — open in browser.
Use when you need to execute R3 (Prototype Generation) in the product requirement Spec process of sdlc-dev, generate requirements/prototype.md based on requirements/prd.md (including task flow + page structure + ASCII wireframe + AC mapping + walkthrough script), and avoid proceeding with generation without context/PRD, using Open Questions instead of verification checklists, or using non-ASCII formats that make the prototype untraceable and unreviewable.
Automatically generate product documentation that complies with Doom framework specifications, supporting PRD transformation, architectural analysis, and multi-type document generation.