Total 43,772 skills, Project Management has 1613 skills
Showing 12 of 1613 skills
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 you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth for execution checklist and status, SSOT), and provide an unambiguous task list for subsequent I2 execution.
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 breaking work into discrete steps, tracking progress through multi-step implementations, or managing implementation task lists. Triggers when an approved plan needs to be converted into tracked tasks, when progress reporting is needed during execution, or when checkpoint reviews are required between task batches.
Sync project state with Linear — detect gaps, consolidate objectives, clean up, route to next action
Read and summarize an existing codebase before any design or implementation work begins. Use as a prerequisite when the project is not greenfield.
Create detailed phase plan (PLAN.md) with verification loop
Produce a detailed low-level design with API contracts, data models, error handling, test strategy, and dependency version policy. Use after the high-level design is approved.
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.
Produce a high-level technical design with architecture diagram, component responsibilities, data flow, and test scenario map. Use after the product intent specification is approved.
Use when you have an approved implementation plan document and need to execute it step by step. Triggers on /execute command, when transitioning from planning with an approved plan, or when resuming execution of a partially completed plan. Provides batch-based execution with TDD, checkpoint reviews, and verification gates.
This skill should be used when the user has a written implementation plan to execute in a separate session with review checkpoints.