Total 30,661 skills, Project Management has 1151 skills
Showing 12 of 1151 skills
Use this skill BEFORE implementing any new feature. This is NON-NEGOTIABLE for scope control. Use when evaluating features during brainstorming, planning new functionality, branches approach size limits (1000/1500/2000 lines, 15/25/30 commits). Do not use when feature is already approved and in progress. DO NOT use when: simple bug fixes with clear scope.
Architecture-aware project initialization combining online research with archetype selection. project initialization, new project, architecture decision, project setup, which architecture, choose architecture, project architecture Use when: initializing a new project and need to select an appropriate architecture based on project type, team size, domain complexity, and current best practices DO NOT use when: architecture is already decided - use project-init instead.
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six Sigma, root cause analysis, strategic decisions, or process improvement.
Senior Agile Facilitator & Delivery Architect for 2026. Specialized in AI-enhanced Scrum orchestration, automated ticket management, and high-velocity sprint coordination. Expert in utilizing LLMs to synthesize daily updates, detect blockers before they arise, and maintain a high-integrity backlog across GitHub Issues, Jira, and linear.
Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.
Used when a Spec Pack is completed, reusable assets need to be promoted to the project SSOT (ADR/contract/ops/NFR/registry), and there are risks of "contaminating the project with full package replication / skipping spec-context / mistaking merge-back for git merge".
Use this when you are about to start Discover for an existing project, but you don't know "which portals can be used as evidence (run/test/ci/contract/ops)" and "which modules should be prioritized (P0/P1/P2)", and you are worried that out-of-control scope will lead to unmaintainable results.
Use when you have confirmed the scope of Discover (P0/P1/P2), and now need to quickly build the Level-0 North Star (memory) and Level-1 map layer index skeleton (components/products) under `.aisdlc/project/`, so that you can supplement evidence by module later without double writing and drift.
Эксперт по статус-отчётам. Используй для создания шаблонов отчётов, executive summaries и project dashboards.
Use when you already have a components map and multiple module pages, and now need to converge business modules (products <= 6), fix the entry points for operation, troubleshooting and rollback (ops), and implement DoD access control and incremental Discover (Delta Discover, stale expiration detection) to ensure the knowledge base is usable and maintainable.
Use when you need to turn selected modules (P0 priority first) into single-page module SSOT at the path `.aisdlc/project/components/{module}.md`, and build authoritative entries for API/Data contracts, invariant summaries, evidence entries and structured Evidence Gaps in the same page to meet the DoD gate requirements of Discover.