Loading...
Loading...
Found 143 Skills
Creates and manages project artifacts (research, spikes, analysis, plans) using templated scripts. Use when asked to "create an ADR", "research topic", "spike investigation", "implementation plan", or "create analysis". Provides standardized structure, naming conventions, and helper scripts for artifact organization. Works with .claude/artifacts/ directory, Python scripts, and markdown templates.
Facilitates collaborative design exploration before implementation. Explores user intent, constraints, and requirements through structured dialogue, then produces an approved design document. Must be invoked when entering plan mode or planning any implementation. Triggers: brainstorm, design, plan, "let's think through," "how should we build."
Project path planning and execution assistant. It helps analyze project requirements, plan execution paths, decompose tasks, identify risks, and manage progress to ensure high-quality delivery of projects.
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
Use this skill BEFORE implementing any new feature. This is NON-NEGOTIABLE for scope control. Use when evaluating features during brainstorming, planning new functionality, branches approach size limits (1000/1500/2000 lines, 15/25/30 commits). Do not use when feature is already approved and in progress. DO NOT use when: simple bug fixes with clear scope.
Use when starting a new project, adding a major feature to an existing system, or when unsure which skills to run and in what order. Supports macOS, iOS, web, full-stack, voice agent, and edge/IoT+ML projects.
Research codebase, write concrete implementation plan. Use after brainstorming.
Help turn ideas into fully formed plans through collaborative dialogue. Use before starting any project - product features, business ideas, creative projects, or process improvements.
Refines a v1 project plan into agent-ready tasks with clear context, implementation steps, and validation criteria. Use after /plan-project has produced a v1 plan.
Conducts structured interviews to derive technical requirements from business requirements. Requires completed business-requirements.yaml as input. Asks targeted technical questions about architecture, technology stack, data model, APIs, security, testing, and deployment. Generates technical-requirements.yaml output.
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Post project updates to team chat, gather feedback, triage responses, and plan next steps. Adapts to available tools (chat, git, issues, tasks). First run discovers tools and saves a playbook; subsequent runs execute from the playbook. Trigger with 'team update', 'post update', 'sync with team', 'standup', 'check team chat', 'feedback loop', 'project update', 'what did the team say'.