Total 50,476 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Project planning and management with CodeSpring. Use when the user wants to work with CodeSpring projects, tasks, PRDs, mindmaps, or analyze a codebase for project planning. Handles workspace selection, project linking, task management, and syncing findings to CodeSpring.
Translate discovered client pain points into high-level technology solution architectures for consulting engagements in Software Engineering, Data Platforms, and AI/ML. Produce solution briefs with phased roadmaps, effort estimations, team composition, and technology recommendations. Use when designing a pre-sale technical solution, creating a solution brief for a proposal, or when a prospect needs to understand what the engagement would look like before committing. This is the preventa técnica / solution engineering step.
Use when the user mentions Geekbot, standups, daily check-ins, async reports, polls, team engagement, response rates, or participation tracking. Triggers on: "standup", "check-in", "report", "poll", "Geekbot", "who hasn't posted", "draft my standup", "team analytics".
Guide spec-driven feature development using a structured three-phase workflow: Requirements → Design → Tasks. Use this skill whenever the user wants to plan a feature, write a spec, or do structured design before coding. Trigger on phrases like "let's spec this out", "write a specification" or "help me think through this feature".
Manages project directory setup and artifact organization. Use when starting a new project, resuming an existing one, or when a PLAN.md needs to be associated with a project directory. Creates the project folder structure (specs/, scripts/, notebooks/) and resolves project naming.
Use when you have a spec or requirements for a multi-step task, before touching code
Use when hierarchical task breakdown is needed, when dependency mapping between tasks is required, when effort estimation and parallelization planning is needed, or when creating work breakdown structures. Triggers on /decompose command, when complex tasks need to be broken into manageable subtasks, when critical path analysis is needed for scheduling, or when identifying tasks that can run concurrently.
Use when starting a new project from scratch, before any technical decisions, to explore the idea through structured sessions and produce a brainstorming synthesis
Navigate the SLDD (Spec Loops Driven Development) process and choose the correct skill for the current stage. Use when starting a new feature or when unsure which step comes next.
Initialize a new project with deep context gathering and PROJECT.md
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
Use when starting any implementation task, feature request, bug fix, or refactoring work. Triggers on /plan command, before any code is written, when requirements need structured analysis, or when transitioning from brainstorming to implementation. Forces question-asking, approach comparison, and explicit approval before any code.