Loading...
Loading...
Found 2,940 Skills
Fetch Jira ticket details from Jira Cloud and prepare for PRD planning. Use when user asks to fetch, load, or work on a Jira issue (e.g., 'Fetch JIRA-123', 'Load issue XYZ-456', 'I'm working on ticket ABC', 'Get details for PROJ-789'). This skill retrieves ticket link, ID, title, and description, then triggers PRD skill to create an implementation plan based on the ticket context.
Sync skills from claude-code-plugins vibe-workflow to this codex-workflow repo. Adapts Claude Code features to Codex equivalents. Use when vibe-workflow has updates to sync.
Use when documentation needs to be updated, clarified, or reorganized to better serve users' jobs-to-be-done with low cognitive load and high signal.
Guides creation of effective Agent Skills with proper structure and validation. Use when users want to create a new skill, update an existing skill, or need guidance on skill design patterns, SKILL.md format, or verify.py implementation. NOT when just using existing skills (use those skills directly).
Execute real actions across 1000+ applications (Gmail, Slack, GitHub, Notion, etc.) using Composio's tool routing. Stop suggesting—start doing.
Initialize projects with AI Dev Flow framework using domain-aware setup
Show status of all features in .dev/. Scans feature folders using parallel agents, generates a status report, and offers to archive completed features.
Format markdown content for Notion import with proper syntax for toggles, code blocks, and tables. Use when formatting responses for Notion, creating Notion-compatible documentation, or preparing markdown for Notion paste/import.
Use when approved Spec Kit `tasks.md` must be executed into implementation changes, or when task execution is blocked by sequencing/checklist gates before feature completion.
Use when work involves Spec Kit and you need to choose the correct `spec-kit-*` sub-skill, enforce artifact-order gates, or route remediation work (for example sequence violations or specification drift at any stage).
Use when an approved Spec Kit `spec.md` must be translated into technical design artifacts (`plan.md`, `research.md`, `data-model.md`, `contracts/`, `quickstart.md`) before `spec-kit-tasks`, or when `plan.md` is missing/outdated after spec or constitution changes.
Use when an approved Spec Kit `plan.md` + `spec.md` must be decomposed into dependency-ordered `tasks.md`, or when `tasks.md` is missing/stale after planning or reconciliation changes.