Total 53,505 skills, Project Management has 1937 skills
Showing 12 of 1937 skills
Apply Sociotechnical Systems Theory to analyze and design work systems through joint optimization of social and technical subsystems. Use this skill when the user needs to diagnose why a technology implementation disrupted work practices, design IT-enabled work systems that balance human and technical needs, or when they ask 'why did this system hurt productivity despite being technically sound', 'how do we design work around new technology', or 'why are people resisting this technically superior system'.
Avaza integration. Manage Organizations. Use when the user wants to interact with Avaza data.
Generates customized client onboarding checklists with phased tasks, ownership assignments, dependencies, acceptance criteria, and email templates. Adapts to consulting, SaaS, or agency engagement models.
When the user wants to plan production or distribution capacity, analyze capacity requirements, optimize resource utilization, or balance capacity with demand. Also use when the user mentions "capacity analysis," "resource planning," "bottleneck analysis," "capacity expansion," "load balancing," "throughput planning," "utilization optimization," or "capacity modeling." For production scheduling, see master-production-scheduling. For long-term network capacity, see network-design.
Generate the competitive analysis section with competitor profiles, SWOT analysis, competitive matrix, differentiation strategy, market share positioning, and sustainable competitive advantage (moat). Proves the business can win against alternatives. Use when building or reviewing competitive analysis sections, benchmarking against competitors, or defining market positioning. Incorporates Farris's competitive metrics, guerrilla positioning strategy, value-based differentiation frameworks, Teece's business model vs strategy distinction (business model = architecture of value creation and capture; strategy = how the model is made difficult to imitate), Kaza's four differentiation types (aesthetic experience, social experience, boundary interactions, purposeful experiences), Ohmae's 3C Strategic Triangle and Key Factors for Success, and the Portable MBA onstage/backstage model with Value Net complementors framework.
Think like Intel's legendary CEO. Apply Andy Grove's management operating system to maximize your team's output through leverage, OKRs, and systematic decision-making. Use when: **Scaling a team** when individual contribution isn't enough; **Performance management** to measure and improve output; **Meeting optimization** to make meetings productive; **Decision-making** in management contexts; **New manager transition** from individual contributor
Initialize a new project — repo, structure, CI, and first commit
Propose a change with optional working artifacts. Use when the user wants a structured proposal with design notes, tasks, and a clear path to implementation.
Issue Workflow Stage 1 — Convert the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Stage 2's responsibility). Meanwhile, this stage is the only official decision point for choosing between the fast track and standard path: Based on the user's description, first review the relevant code; if the root cause can be identified at a glance and the required changes are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "record this bug", "I found a problem". This is the starting point of the issue workflow with no pre-dependencies.
Document the finalized tech stack selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent records. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four categories: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively trigger after making important choices during feature-design or issue-analyze, or when the user says "record the decision", "archive tech selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive proposed solutions under discussion.
Draft a structured decision memo for Ane. Use when the user asks for a "decision memo", "decision doc", "options paper", "recommendation brief", or equivalent. Produces a scannable document with context, options, recommendation, risks, and reversibility. Applies Ane's CLAUDE.md writing style automatically.
Full task lifecycle: create → assign → monitor → review → reject/complete. Use when asked to "add a feature", "fix a bug", "create a task", "加个功能", "修个 bug", or "/ak-task <description>".