design-handoff
Design-to-development handoff process
发现 tools project management 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Design-to-development handoff process
Structured planning from discovery to executable plans
Project roadmap documentation
Break down features into implementable tasks
Produce a thorough plan before implementation. Use for planning tasks: clarify unknowns, create plan iterations based on confidence level, validate each, then finalize.
Quality assurance workflow and testing process
High-level decision making, roadmap planning, and resource prioritization.
User behavior tracking, event logging, and analytics dashboards
Create Design Document - generates a technical design document based on the requirements document
Quarterly planning process for roadmap and resource allocation
Transform ideas into comprehensive product specifications and user stories
Standardize how to build new features from planning to documentation. Use when starting a new user story, feature request, or epic.
Structured discussion to clarify requirements before planning
Setting effective Objectives and Key Results (OKRs)
Collaborative solution architecture and design discussions. Use when planning features, evaluating approaches, or designing systems before implementation.
Design productivity dashboards, task management interfaces, and market intelligence platforms optimised for ADHD users. Apply when building UIs requiring cognitive load reduction, single-task focus modes, execu...
Create and manage step-by-step execution plans from architecture documents. Use after brainstorming to bridge design and implementation.
Maintain consistent UI/UX, enforce design system usage, and ensure accessibility/responsiveness. Use when designing screens, styling components, or reviewing UI implementation.
Capture risks, assumptions, and mitigation plans throughout delivery.
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-r...
Capture loosely structured ideas, enrich with research, and create backlog issues. Use when user has a raw concept that needs fleshing out.
Developer role responsible for implementation, KB search, design review, atomic commits, and compound learning. Activate when writing code or fixing bugs.
Create comprehensive feature specifications for Claude Code projects using iterative refinement with ISO/IEC/IEEE 29148:2018 criteria. Use when user requests creating a technical specification (ТЗ) for a new fe...
Activates when user requests architecture analysis, code review, refactoring suggestions, design pattern evaluation, or SOLID principles assessment. Do NOT use for security-specific audits (use security-auditor...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。