Total 54,043 skills, Project Management has 1965 skills
Showing 12 of 1965 skills
Progressively gather requirements through automated codebase discovery and yes/no questions, then generate a comprehensive requirements spec. Use when starting a new feature, planning a build, or when you need structured requirements before implementation.
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for board meetings, dissects decisions with no good options, forces honest post-mortems, and identifies blind spots before competitors or board members do. Use when you need plan validation, board preparation, hard decision frameworks, assumption stress-testing, failure analysis, or when user mentions stress test, challenge, board prep, hard decision, pre-mortem, post-mortem, devil's advocate, plan review, or executive coaching.
Create or restructure a persistent milestone-based roadmap under .spec-driven/roadmap/.
Apply systems thinking — causal loop diagrams, stock-and-flow models, system archetypes, and leverage-point analysis — to organizational, economic, or social problems where feedback loops, delays, or emergent behavior drive recurring failure across multiple interacting actors. Use this skill when the user describes a multi-actor situation that resists linear fixes: policy interventions that backfire, org-level fixes that break other teams, market symptoms that return after being solved, or time-lagged second-order consequences, even if they say 'why does fixing X make Y worse' or 'identify the leverage points in this system'. Do NOT use for single-cause software bugs, flaky tests, or regressions — those are debugging problems, not systems-thinking problems, even when phrased as 'this keeps coming back'.
The meta-framework for how a company runs -- the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse design, issue resolution (IDS), 90-day rocks, and communication cadence. Use when setting up company operations, selecting a management framework, designing meeting rhythms, building accountability systems, implementing OKRs, or when user mentions EOS, Scaling Up, operating system, L10 meetings, rocks, scorecard, accountability chart, quarterly planning, or meeting cadence.
With 'Dao' as the overall controller, consolidate capabilities such as planning, game design, game visual design, general design, review, implementation, summary, and repository maintenance into a unified entry, and call internal modules as needed.
Morning preparation. Calendar lookahead, meeting context loading, open threads from yesterday, active task review. Extends briefing with actionable prep.
Query and operate ZenTao data via the zentao command-line tool, covering CRUD operations and status transitions for modules including program, product, project, execution, story, Bug, task, testcase, testtask, productplan, build, release, feedback, ticket, system, user, and attachment. Use this skill when users mention ZenTao, zentao, querying project progress, obtaining Bug lists, creating tasks, updating requirement status, and other project management operations.
Use when you have a rough idea and want to refine it into a well-formed proposal before submitting to Nexus. Must check directive first - all ideas must align with current organizational focus.
Scores completed OKR sets at cycle close with KR-level scoring per the canonical OKR type enum (committed | aspirational | learning | operational_health | compliance_or_safety), committed-vs-aspirational interpretation, evidence quality assessment, learning synthesis, and next-cycle recommendations. Refuses to retroactively change targets or shrink committed scope, average away guardrail KRs, treat 0.7 as success for committed or compliance_or_safety KRs, equate effort with impact, or use scores for individual performance. Hands off to iterate-lessons-log, iterate-retrospective, define-hypothesis, measure-dashboard-requirements, measure-instrumentation-spec, and foundation-okr-writer.
Event Storming 기법을 사용하여 PlantUML 시퀀스 다이어그램을 작성하고 유저스토리 개발을 준비합니다. 기획 구체화 시 사용하세요.
Use Case 2.0 methodology by Ivar Jacobson. Covers use case slices, lightweight documentation, user story derivation, and value-driven prioritization. Modern approach to use case modeling for agile teams.