Total 53,554 skills, Project Management has 1940 skills
Showing 12 of 1940 skills
Use this skill when creating new files that represent architectural decisions — data models, infrastructure configs, auth boundaries, API contracts, CI/CD pipelines, or event systems. Flags irreversible decisions and forces a discussion about trade-offs before committing.
Execute the implementation plan, track progress in the task backend. Use after planning.
Explore codebase, write spec + battle plan — zero questions, pure code research
Stress-test plans, proposals, and strategies. Use for pre-mortems, assumption audits, risk registers, evaluating business ideas, identifying failure modes, or when you need devil's advocate analysis before committing resources.
Build a personalized learning roadmap with milestones and practice checkpoints
Review an implementation against task file requirements. Checks every spec scenario and Done When criterion, identifies gaps, and reports them. Use when the user says "task compliance", "check compliance", "review against the task", or to verify implementation completeness before shipping.
Use when the user wants to brainstorm an idea or design a feature/spec. Explores intent and requirements through dialogue, then writes a spec document to docs/spark/ and STOPS. Does not auto-chain to implementation planning or any other skill.
Implement PRDs/specs with a mandatory precheck review before coding. Use when a user asks to implement a PRD/feature spec/requirements doc or says "implement PRD/spec". Perform a preflight review, raise questions on scope/consistency/risks, then implement after confirmation.
Create outcome spec (overview, decisions, steps, edge cases). Use $ARGUMENTS as spec topic if provided.
Use when you need to perform I2 (Implementation Execution) in the Spec Pack of sdlc-dev, implement in batches with `{FEATURE_DIR}/implementation/plan.md` as the only SSOT, run minimal verification, write back audit information, and report at batch checkpoints; stop immediately when encountering blocking or clarification required items.
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
Zoho Sprints integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zoho Sprints data.