requirements-gathering
(opencode-project - Skill) Template and guidelines for creating comprehensive requirements specifications
(opencode-project - Skill) Template and guidelines for creating comprehensive requirements specifications
Plan and structure effective meetings with agendas and follow-ups
Expert software engineering lead who translates product requirements into comprehensive engineering plans using GitHub Projects. Reviews PRDs and user stories, identifies gaps and conflicts, pushes back constructively on poor requirements, applies software engineering best practices, creates detailed technical plans with tasks and milestones, and ensures production-ready architecture. Use when translating product specs into actionable development plans, validating requirements, or designing system architecture.
Agile sprint planning toolkit. Create user stories following INVEST criteria, plan sprints with capacity management, define acceptance criteria, and track dependencies across sprints for incremental software delivery.
Use when building zero-to-one products, when the solution shape is undefined, or when teams are applying growth metrics too early
Local-first, multi-product backlog management with agent collaboration discipline.
Break down epics into implementable user stories with acceptance criteria, estimates, dependencies, and sprint groupings. This skill should be used for epic planning and backlog grooming.
Create comprehensive Product Requirements Documents (PRDs), break down features into epics and user stories, and establish clear acceptance criteria. Use this skill when you need to: (1) Transform a project brief or business requirements into a structured PRD, (2) Define product scope and goals, (3) Create user stories with acceptance criteria, (4) Break down complex features into implementable epics, (5) Prioritize features and determine MVP scope, (6) Specify non-functional requirements, or (7) Translate business vision into development-ready specifications.
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
Use after brainstorming, before implementation. Breaks work into discrete, actionable tasks with clear verification points.
Master stakeholder communication with presentations, status updates, expectation management, and effective collaboration techniques for product success.
차별화된 프로덕션 수준의 프론트엔드 UI 설계 및 구현. Use when (1) UI/UX 디자인 필요, (2) 컴포넌트 디자인, (3) 화면 설계 및 구현, (4) Design Thinking 기반 프론트엔드 개발.
Use when asked to "growth loops", "build a growth engine", "design a viral loop", "create a content loop", "move beyond paid acquisition", or "why isn't growth compounding". Helps design self-reinforcing growth systems where output becomes input. The Growth Loops framework (from Brian Balfour / Reforge and Elena Verna) shifts thinking from linear funnels to compounding loops.
A quality control mechanism with a designated interviewer from outside the hiring chain who has veto power to ensure candidates raise the bar (better than 50% of current employees in role). Amazon's talent density secret.
Comportamientos y apariencias consistentes mejoran la usabilidad. Use cuando establezca patrones de diseño, defina guidelines, o evalúe coherencia del sistema.
Mantiene patrones visuales y de comportamiento uniformes en toda la interfaz. Use cuando diseñe sistemas de diseño, defina patrones de interacción, o evalúe coherencia entre pantallas.
Creating effective developer onboarding experiences
Building thought leadership through publishing, speaking, and industry influence
WCAG 2.2 Level AA compliance patterns for Rails applications including ARIA implementation, keyboard navigation, focus management, screen reader support, and color contrast requirements. Use this skill when implementing any user-facing UI to ensure accessibility compliance. Trigger keywords: accessibility, a11y, WCAG, ARIA, screen reader, keyboard navigation, focus, color contrast, disability, assistive technology
A human-centered system for attributing creative contributions across any medium, where containers provide structure and conversations determine value
Use when asked to "radical candor", "give feedback that cares", "have a difficult conversation", "challenge directly", "manage performance issues", or "give praise that lands". Helps deliver direct feedback while showing you care. The Radical Candor framework (created by Kim Scott) teaches how to challenge directly while caring personally.