Loading...
Loading...
Found 202 Skills
Asana Task Creator - Auto-activating skill for Enterprise Workflows. Triggers on: asana task creator, asana task creator Part of the Enterprise Workflows skill category.
Status Report Generator - Auto-activating skill for Enterprise Workflows. Triggers on: status report generator, status report generator Part of the Enterprise Workflows skill category.
Create and manage structured meeting notes with automatic action item extraction and governance integration. Use when user mentions "meeting notes", "record meeting", "create meeting", "standup", "retrospective", "planning", or any meeting-related keywords.
Unified requirement clarification to prevent downstream implementation churn by resolving ambiguity early. Default: research-first with autonomous decision-making and persistent questioning. --light: direct iterative Q&A. Triggers: "cwf:clarify", "clarify this", "refine requirements"
This skill should be used when users need to manage Linear issues, tasks, or projects via command line. Triggers on requests mentioning Linear issues, issue tracking, creating issues, updating issue status, managing Linear projects, or Linear CLI operations.
Traditional development workflow skill for product requirement intake, engineering research, technical planning, task breakdown, implementation, testing, bugfix loop, and engineering review. Use when a user wants to run or continue a structured software delivery workflow that mirrors real product-development collaboration.
End-of-day structured summary and next-session prep. Use at the end of each working day or significant work block.
Spec-driven development: plan → go → review loop with spec lifecycle states and a project-level feature ledger. Use for planning features, implementing from specs, refining specs, tracking what features exist across specs, and resuming work. Trigger on requests mentioning specs, requirements/design/tasks, spec-help, spec-plan, feature ledger, FEATURES.md, spec-ledger, `.kiro`. IMPORTANT: Never edit spec files without first reading this skill.
Maps multi-phase trajectories with dependencies into clear, sequenced roadmaps. Use when work has multiple phases that need sequencing, when decisions today affect future decisions, when stakeholders need to see the whole journey, or when external dependencies exist. Applicable regardless of total duration — a 4-week multi-phase initiative benefits as much as a quarterly roadmap.
Executes project delivery in five phases (analysis, planning, implementation, validation, delivery) with checklists and a structured final report. Use when the user asks to execute a phase, deliver Phase 1, run a methodological delivery, or follow phased execution.