Total 53,816 skills, Project Management has 1953 skills
Showing 12 of 1953 skills
The YC meta-game distilled from 4000+ funded companies. Demo day prep, batch dynamics, investor updates, "launch now" mentality, talking to users obsessively. This is the playbook that turned $125K checks into trillion-dollar companies. Use when "yc, y combinator, demo day, batch, investor update, office hours, launch now, talk to users, do things that don't scale, make something people want, startup school, yc application, series a prep, post-yc, yc, startup, accelerator, demo-day, fundraising, launch, users, growth" mentioned.
Startup and life advice channeling Paul Graham's essays, YC experience, and Twitter wisdom. Use this skill when: (1) Evaluating startup ideas or finding new ones (2) Early-stage strategy and user acquisition (3) Growth and survival decisions (default alive?) (4) Fundraising and investor relations (5) Founder leadership and team building (6) Avoiding common startup mistakes (7) Career and life decisions Invoke with /paul-graham or auto-triggers for startup advice topics.
Create a Delegation Pack (delegation brief, decision rights, context handoff, check-in cadence, review plan, debrief). Use for delegation, letting go, empowering reports, and avoiding micromanagement.
Create comprehensive steering documents for development projects. Generates project-specific standards, git workflows, and technology guidelines in .kiro/steering/ directory.
Use when creating or amending a Spec Kit project constitution, especially when `memory/constitution.md` is missing, contains `[PLACEHOLDER]` tokens, or principle changes must be propagated to planning/spec/task templates.
Structured interactive questionnaire framework for gathering requirements from users. Uses A/B/C/D/E multiple choice patterns with additive vs exclusive question classification.
Documentation-driven project development workflow. Intelligently determines task types, executes existing plans or generates new plans using feature-dev. **Use Cases:** - Complete project documentation exists, need to execute development tasks - User specifies to execute a certain plan (e.g., "Execute plan 001") - User requests to develop new features (automatically uses feature-dev to generate plans) **Prerequisites:** - The project should already have a docs/ documentation structure (PRD, SAD, etc.) - For new projects, it is recommended to first use the project-docs-setup skill to create complete documentation - If plan formulation is needed, it is recommended to use the project-planning skill **Relationship with Other Skills:** - project-docs-setup: Creates project documentation structure - project-planning: Formulates development plans (requirement clarification + design discussion + plan writing) - project-workflow: Executes development plans + updates documentation - Recommended workflow: project-docs-setup → project-planning → project-workflow **Trigger Methods:** - "Execute plan 001" / "Continue 001-user-authentication" - "Start development" / "Execute plan" / "Continue last task"
Planning Agent: Converts project intent into a detailed execution plan. Responsible for defining detailed scope, WBS, dependencies, schedule, budget, and resource planning. Use after Intake/Charter is approved.
Atlassian Administrator for managing and organizing Atlassian products, users, customization of the Atlassian suite, permissions, security, integrations, system configuration, and all administrative features. Use for user provisioning, global settings, security policies, system optimization, and org-wide Atlassian governance.
Use when planning high-stakes initiatives (migrations, launches, strategic changes) that require clear specifications, proactive risk identification (premortem/register), and measurable success criteria. Invoke when user mentions "plan this migration", "launch strategy", "implementation roadmap", "what could go wrong", "how do we measure success", or when high-impact decisions need comprehensive planning with risk mitigation and instrumentation.
Use to set cadences, decision logs, and escalation paths for enterprise pursuits.
Use to convert creative briefs into actionable task plans with owners and SLAs.