Total 52,363 skills, Project Management has 1913 skills
Showing 12 of 1913 skills
Creates implementation-ready blueprints for new software products, features, apps, and internal tools. Use when starting a greenfield project, major feature, or technical handoff that needs PRD, TRD, architecture, schema, security, modules, rules, phases, design, and memory docs.
Adversarially stress-test a plan or design until every load-bearing assumption is defended or the plan is rejected. Use when the user wants to be grilled, pressure-tested, or "grill-me-thermonuclear". NOT for generative brainstorming, affirmation, light polish, or executing an already-settled plan.
Reconcile the project's FPF state with recent repository changes
Systematic Fishbone analysis exploring problem causes across six categories
Transform feature descriptions into well-structured project plans following conventions
Execute work plans efficiently while maintaining quality and finishing features
Explore requirements and approaches through collaborative dialogue before planning implementation
[BETA] Transform feature descriptions or requirements into structured implementation plans grounded in repo patterns and research. Use when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', or when a brainstorm/requirements document is ready for technical planning. Best when requirements are at least roughly defined; for exploratory or ambiguous requests, prefer ce:brainstorm first.
2. Create Feature Design Document
Proactive requirements gathering - systematically interviews the user to uncover ambiguities, preferences, and constraints BEFORE implementation begins.
Gate 0 research phase for pre-dev workflow. Dispatches 4 parallel research agents to gather codebase patterns, external best practices, framework documentation, and UX/product research BEFORE creating PRD/TRD. Outputs research.md with file:line references and user research findings.
Gate 6: Technology choices document - explicit, versioned, validated technology selections with justifications. Large Track only. HARD BLOCK: Must load Ring Standards and PROJECT_RULES.md before proceeding.