Loading...
Loading...
Found 81 Skills
Use this before touching code when you have a requirement for a specification or multi-step task
Conduct design interviews, generate five distinct UI variations in a temporary design lab, collect feedback, and produce implementation plans. Use when the user wants to explore UI design options, redesign existing components, or create new UI with multiple approaches to compare.
Analyzes PRD documents, concept briefs, or feature specs and creates structured implementation plans with visual kanban tracking. Breaks requirements into epics, stories, and tasks with dependencies and estimates. Outputs to `.claude/` folder for integration with project-harness and other skills. Generates PROJECT.md for shared project context.
Use when creating implementation plans for features or tasks. Focuses on tactical execution planning with clear tasks, dependencies, and success criteria.
Conduct structured policy analysis including problem definition, alternative evaluation, and evidence-based recommendation. Use this skill when the user needs to evaluate policy options, compare interventions, assess regulatory impact, or make public sector recommendations — even if they say 'which policy should we adopt', 'what's the best approach to this public problem', or 'evaluate these policy alternatives'.
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
Plan work before coding: do repo research, analyze options/risks, and ask clarifying questions before proposing an implementation plan. Use when the user asks for a plan, design/approach, scope breakdown, or implementation steps.
Fetches Jira ticket context, creates a branch, and drafts an implementation plan
This skill should be used when the user wants to identify the single highest-impact improvement to make to their project. Triggers on requests like "what should I build next", "innovate", "best improvement", "next big thing", or when seeking the most compelling addition to a codebase.
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
Create phased implementation plans from research findings. Invoke when a task needs an implementation plan.
Write technical specifications that give agents enough context to implement features while leaving room for autonomous research and decision-making. Use when planning features, documenting architecture decisions, or creating implementation guides.