Total 50,476 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.
Pre-Production validation — build a production-quality end-to-end build to confirm the full game loop is achievable before committing to Production. Run after GDDs, architecture, and UX specs are complete. Produces a PROCEED/PIVOT/KILL verdict that gates the Pre-Production → Production transition.
Scaffold and maintain a reusable research → design → plan → orchestrate → act folder for any non-trivial work — software features, marketing campaigns, org changes. Drops a domain-agnostic spine (00-README · 01-plan · 02/03 research · 04-discussion newest-first · 05-tracking · 09-orchestration · artifact/board.html plan-board) plus stateless action-skills that augment the docs in place without clobbering hand-written prose. Composes ikenga-artifact-builder, huashu-design, frontend-design, ikenga-pkg-builder when present; degrades gracefully when not. Profile-driven: `software` (rich default, code work), `general` (lean, non-code — campaigns, org changes), and `content` (editorial/marketing with key art). TRIGGER when the user asks to start a real plan for non-trivial work ("plan a feature," "scaffold a plan folder," "set up groundwork for…"), references an existing plans/ folder by groundwork structure, or runs any of these actions: groundwork init / research / design / review / clarify / orchestrate / refresh-board / refresh-living-spec / status. DO NOT TRIGGER for one-off code changes, single-document writeups, ADRs, or content that fits in a single markdown file — those don't need a multi-doc plan folder. If the user just wants a single artifact (dashboard, mockup), route to ikenga-artifact-builder instead.
Owner-scoped task decomposition with gates, rollback, verification commands, and smoke tests.
Inspeccionar un proyecto existente para descubrir decisiones arquitectónicas implícitas y proponer ADRs candidatos. Usar cuando el usuario quiera auditar un repositorio en busca de decisiones no documentadas, pida "descubrir ADRs", "qué decisiones arquitectónicas tiene este proyecto", "busca ADRs en el repo", "analiza la arquitectura del proyecto" o cualquier variante que implique explorar el código/estructura para inferir decisiones relevantes que merezcan un ADR. Activar también cuando el usuario llegue a un proyecto nuevo y quiera entender qué decisiones ya se tomaron, aunque no mencione explícitamente "ADR".
Crea o actualiza tareas técnicas (TK-XXX) asociadas a una historia de usuario existente. Activar cuando el usuario solicite planificar implementación, descomponer trabajo, definir alcance técnico, estructurar subtareas o documentar especificaciones técnicas sin generar código ni pruebas. Activar también — por defecto — cuando el usuario solo entregue una referencia a una historia (p. ej. «US-004», «planifica US-007», «tareas para esta historia») — en ese caso el propósito es proponer stubs agrupados por unidad de trabajo que cubran los escenarios (SC-XX) y consideren las reglas de negocio (BR-XX) de la US, sin redactar TKs completas.
Creates a new Linear issue from a free-form description. Drafts a structured title and body, picks team/project/labels/priority from the connected workspace, shows the draft to the user for approval, then creates the ticket. Use when the user asks to "create a Linear ticket", "file an issue", "make a ticket", "open an issue in Linear", or any request to log a new bug/feature/task.
Deterministic plan lifecycle management via scripts/plan-manager.py: create, track, check, complete, and abandon task plans. Use when user says "/plans", needs to create a multi-phase plan, track progress on active plans, or manage plan lifecycle (complete, abandon, audit). Do NOT use for one-off tasks that need no tracking, feature implementation, or debugging workflows.
Collaborative design phase for feature lifecycle: explore requirements, discuss trade-offs, produce design document. Use when starting a new feature that needs design before implementation. Use for "design feature", "let's think through", "explore approaches", or "/feature-design". Do NOT use for simple bug fixes or tasks that don't need design discussion.
SPARC development workflow: Specification, Pseudocode, Architecture, Refinement, Completion. A structured approach for complex implementations that ensures thorough planning before coding. Use when: new feature implementation, complex implementations, architectural changes, system redesign, integration work, unclear requirements. Skip when: simple bug fixes, documentation updates, configuration changes, well-defined small tasks, routine maintenance.
Scope and assess new feature ideas → living doc with go/no-go. Elaborates vague ideas into clear concepts. First pipeline step. Triggers: user wants to add/build/implement any new capability. Not for: bugs (triage-issue), requirements (define), design (design/architect).
Suggest what to work on next based on project state and session context. Considers proximity, momentum, status, and constraints.