Total 50,405 skills, Project Management has 1845 skills
Showing 12 of 1845 skills
Zoho Sprints integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zoho Sprints data.
Claiming work is complete without verification is dishonesty, not efficiency. Use when ANY variation of success/completion claims, ANY expression of satisfaction, or ANY positive statement about work state.
Turn a roadmap milestone Planned Changes item into a normal spec-driven change scaffold.
Nifty integration. Manage Organizations. Use when the user wants to interact with Nifty data.
Apply Stakeholder Theory (Freeman, 1984) and the Mitchell et al. (1997) salience model to identify, classify, and prioritize stakeholders based on power, legitimacy, and urgency. Use this skill when the user needs to map stakeholders for a project or strategy, determine which stakeholders demand immediate attention, balance competing stakeholder interests, or when they ask 'who are our key stakeholders', 'how do we prioritize conflicting demands', or 'which stakeholders can block this initiative'.
Break an approved spec into ordered implementation tasks with dependencies, sequencing logic, and done criteria.
Document finalized technology selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent documents. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four types: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively push when important choices are made after feature-design or issue-analyze, or when the user says "record decision", "archive technology selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive under-discussion solutions.
신규 프로젝트 모듈 구조 + _common 기본 구성 세팅 스킬. "프로젝트 세팅", "모듈 구조 잡아줘", "초기 구성", "프로젝트 초기화" 키워드로 트리거. DB 설계 완료 후, 최초 1회 실행.
Comprehensive A3 one-page problem analysis with root cause and action plan
Iterative PDCA cycle for systematic experimentation and continuous improvement
Turn a spec or requirements into a bite-sized implementation plan. File-structure-first (deep modules), embedded grill to stress-test, no forced sub-skill chains. Use when you have a spec or clear requirements and are ready to plan execution.
Clarify intent, propose 2-3 approaches, embedded grill to stress-test the chosen path. Use before any creative work — new features, components, behavior changes, design questions. Mockup-only requests use mockup quick-mode (no spec/plan ceremony).