Total 52,912 skills, Project Management has 1929 skills
Showing 12 of 1929 skills
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, which can be accessed by both AI and humans when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — including bugs, configuration traps, environment issues, and integration failures; The knowledge track records findings that "should be the default approach going forward" — including best practices, workflow improvements, and reusable patterns. Trigger scenarios: Proactively prompt at the end of feature-acceptance or issue-fix workflows, or when the user mentions phrases like "document knowledge", "learning", "document learnings", or "record this experience". Spec documents record what was done, while learning documents record what pitfalls were encountered / what was learned — they complement each other and are not interchangeable.
Used when users want to analyze task scheduling, personnel distribution, man-hours, and risk status under a specific TAPD requirement.
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Zoho Bugtracker integration. Manage Projects. Use when the user wants to interact with Zoho Bugtracker data.
Systematic Fishbone analysis exploring problem causes across six categories
Facilitate methodical review of proposals (technical designs, product specs, feature requests). Use when asked to "review this proposal", "give feedback on this doc", "help me review this RFC", or when presented with a document that needs structured feedback. Handles markdown files, GitHub gists/issues/PRs, and other text formats. Chunks proposals intelligently, predicts reviewer reactions, and produces feedback adapted to the proposal's format.
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session recovery after /clear.
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.
Evaluate and cast one or more high-quality votes on pending ideas when probe next routes vote.
Provides situational playbooks for high-stakes edge cases that don't fit the standard management toolkit — produces step-by-step guidance for inappropriate team behavior, an engineer badmouthing your manager, letting someone go when circumstances are hard, manager quitting guilt, and handling layoffs (for both those leaving and those staying). Use when the user says "don't know how to handle this," "someone said something inappropriate," "engineer said something offensive," "developer talks badly about my manager," "letting someone go when their situation is hard," "I feel guilty about leaving my job," or "handling a layoff." Do NOT use for standard underperformance management (use performance-reviews) or giving direct feedback (use feedback).
/cs:office-hours <topic> — YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit.
Track subcontractor payments, lien waivers, and compliance. Manage payment schedules and documentation.