Total 50,474 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Set up a project's meta-structure for agentic engineering — CLAUDE.md, AGENTS.md, docs/, README, and CHANGELOG. Use when starting a new project or retrofitting an existing codebase for the forge workflow.
Manage the academic workspace — project structure, templates, and output organization.
Semantic validation patterns for PROJECT.md alignment (GOALS, SCOPE, CONSTRAINTS, ARCHITECTURE)
Linear ticket lifecycle for any project. Use when starting work on a Linear issue, ending work on an issue, or asking what to work on next. Triggers: start KAT-N, pick up, implement, finish, complete, done with, close, what's next, next ticket, next issue. Handles blocker validation, status transitions, context loading, branch creation, evidence gating, and chain promotion.
Drafts initial ticket requirements by asking targeted clarifying questions and producing a structured ticket with Title, Body, and Acceptance Criteria. Use when a user has a request that needs to be converted into a clear tracker-ready ticket without codebase or architecture analysis.
Create a living specification (Spec) or plan for a feature by analyzing requirements and codebase
Create a new track with specification and phased implementation plan
Plans PM career growth using frameworks from 40+ career episodes and Ami Vora's advancement strategies. Use when planning promotions, identifying skill gaps, navigating career transitions, or choosing between IC and management paths.
Beans-driven Ralp loop for beans-enabled repos. Use either to work on one bean on user request or to work on all beans in a repo.
Track and manage recruiting pipeline stages. Trigger with "recruiting update", "candidate pipeline", "how many candidates", "hiring status", or when the user discusses sourcing, screening, interviewing, or extending offers.
Convert project plans to JSONL format (issues + dependencies). Use when users ask "convert plan to jsonl", "create jsonl from plan", "export plan as json" or "convert plan to taks", "create tasks from plan", "export plan as tasks".
Transform specifications into actionable implementation plans with phases, tasks, and acceptance criteria. Use when: (1) User asks to create/write an implementation plan, (2) User asks to plan implementation from a specification, (3) Converting specifications from .workflows/specification/{topic}/specification.md into implementation plans, (4) User says 'plan this' or 'create a plan', (5) Need to structure how to build something with phases and concrete steps. Creates plans in .workflows/planning/{topic}/plan.md that can be executed via strict TDD.