Discover tools project management skills, compare source repositories and read the instructions for each workflow.
Use to validate process documentation. Apply TDD to skill writing: RED (run without skill, document failures) → GREEN (write skill) → REFACTOR (close loopholes). Test under pressure: time constraints, sunk cost...
Use when finishing any task. Final checklist before marking complete. Ensures nothing forgotten, all tests pass, documentation updated.
Use when decomposing complex work. Dispatch fresh subagent per task, review between tasks. Flow: Load plan → Dispatch task → Review output → Apply feedback → Mark complete → Next task. No skipping reviews, no p...
Use when setting up CI/CD pipelines. Teaches pipeline design principles and references platform-specific templates.
Use when implementing a multi-step plan. Execute systematically with verification checkpoints to catch errors early.
Use after brainstorming, before implementation. Breaks work into discrete, actionable tasks with clear verification points.
Cloud monitoring with Prometheus, Grafana, and cloud-native tools. Use when setting up metrics, alerts, dashboards, or troubleshooting performance issues.
MANDATORY: Use gh (GitHub) or glab (GitLab) CLI for ALL issue/task management. Unified workflow across platforms.
Use when starting new features, major changes, or unclear requirements. Establishes shared understanding before implementation.
Check for relevant skills before starting any task
Technical pre-sales and solution design for Nimble consulting proposals. Use when creating or populating one-pager documents, drafting scope of work or SOW proposals, defining team compositions and sizing, prep...
Comprehensive guidance for writing user stories following Nimble's product development standards. Use when creating product requirements, organizing backlogs, writing user stories, documenting bugs, or creating...
Create product requirements using Linear's native structure. Use when creating or editing Initiatives, Projects, Milestones, Project Documents (specs), or Issues (user stories) in Linear. Triggers include reque...
Guide for creating Product Requirements Documents (PRDs) following Nimble's standard. Use when creating new PRDs, defining requirements, documenting features, or planning product releases. Covers structure, AI-...
Literate UI/UX for product teams - accelerate from idea to working prototype in minutes using markdown with embedded interactive React components. Use for fast iteration and async collaboration on product specs...
Generate comprehensive Product Requirements Documents with interactive discovery, progress tracking, and True Ralph Loop support for autonomous implementation. Use when user wants to (1) create a PRD for a new...
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature,...
Manages Basecamp todos, cards, messages, and projects using the bc4 CLI tool. Use when the user mentions Basecamp, asks about todos or tasks on a card table, wants to create or update Basecamp items, or referen...
After generating a plan for the user, use this skill to save the plan to the project.
Discover available Jira fields for a project and issue type. Use when the user needs to find field names, see what fields are available, or discover custom field values before creating or updating tickets.
View Jira ticket details to understand requirements and context. Use when the user mentions a ticket key, wants to understand a task, needs to load ticket context, or starts work on an issue.
Get comments from a Jira ticket to review discussion history. Use when the user wants to see ticket comments, check for updates, review feedback, or understand the discussion on an issue.
Create a new Jira ticket. Use when the user wants to create a task, bug, story, or any other issue type in Jira.
Manage Jira ticket attachments. Use when the user wants to list, upload, download, or delete attachments on a ticket.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.