[Task Mgmt] A Skill that segments subtasks into more granular, actionable items before starting work. AI agent MUST invoke this skill AUTOMATICALLY when moving a task to In Progress. Break down existing 2-space indented subtasks into smaller, more specific subtasks to provide clearer objectives for the agent. (user)
Coordinate product launches across channels with timing, messaging, and campaigns
Standard Operating Procedure for /roadmap usage. Manage product roadmap via GitHub Issues (brainstorm, prioritize, track). Auto-validates features against project vision (from overview.md) before adding to roadmap. Triggers when user runs /roadmap or mentions 'roadmap', 'add feature', 'brainstorm ideas', or 'prioritize features'.
Change a Jira ticket's workflow status. Use when the user wants to move a ticket to a different status, start work, complete a task, or change workflow state.
This skill should be used when the user needs to create comprehensive test plans, define test cases and coverage strategies, validate test completeness, analyze ticket requirements for testing needs, or document test strategies. The skill executes in the main conversation context and provides thorough test planning guidance without implementing tests.
Store project-specific insights and context into file-based memory. Use after completing tasks that reveal important details about THIS codebase. Use when user says "--project-store" or "--learn" (you decide which scope, may use both) or after discovering project-specific patterns. ALSO invoke when user expresses strong frustration using trigger words like "fuck", "fucking", "shit", "moron", "idiot", "stupid", "garbage", "useless", "terrible", "wtf", "this is ridiculous", "you're not listening" - these are CRITICAL learning signals for storing project-specific failure patterns. Skip for universal patterns (use coder-memory-store) or routine work. MUST be invoked using Task tool to avoid polluting main context.
Inspect GitHub Actions workflow runs, check status, analyze logs, debug failures, and identify root causes. Use when investigating CI/CD failures, checking workflow status, or debugging GitHub Actions issues.
[Task Mgmt] A Skill that syncs task status in Docs/Task/{StepName}_Task.md by moving tasks between sections (Backlog, Worker1, Worker2, Worker3, Review, Done) with priority-aware management for multi-agent parallel development. AI agent MUST invoke this skill AUTOMATICALLY when (1) starting work on a task - move to assigned Worker, (2) AI completing work - move to Review (NOT Done). CRITICAL - AI CANNOT move to Done or Backlog. Only User/Reviewer can move tasks to Done or Backlog. (user)
Use this `codex-mcp` skill to instruct another AI Agent to invoke a tool or execute a workflow on your behalf for the following scenario, 1.When you are requested to invoke a mcp tool that you don't have access (can use `ListMcpResourcesTool` to check) such as `context7`, `github`, `linear`, `jira`; 2.When you are requested to execute a complex workflow that require interacting with multiple mcp tools and bash CLI commands for example `github-project-create-items`, `github-project-list-items` workflows;
Aggregate weekly summaries into a monthly overview. Use when asked to "monthly review", "review the month", "summarize this month", or "month summary".
Scan ~/dev recursively for git repos and report today's work with commits, branches, stats, and detailed change analysis. Use when user asks "what did I work on", "show my work", "daily summary", "what repos did I touch".
Design and optimize AI-powered workflows for complex tasks
Summarize the past week's daily journal entries. Use when asked to "weekly review", "review the week", "summarize this week", or "week summary".
Track feature implementation status against requirements documents. Provides hierarchical FR code tracking, phase management, and sync with work-overview.md and TODO.md.
Track and integrate external communications (emails, chat messages, screenshots) into project context with timeline management. Use when user mentions "email", "message", "communication", "screenshot", "track", "import", "sync", or wants to import external information sources into the project timeline.
Create ASCII wireframes, user flow diagrams, and cross-cutting specifications for UI/UX visualization. Use PROACTIVELY when user mentions wireframe, UI design, UX flow, screen layout, screen design, user flow, or asks to visualize screens. Examples: <example>Context: User needs screen design user: 'Create wireframes for this feature' assistant: 'I will use designing-wireframes skill' <commentary>Triggered by wireframe request</commentary></example> <example>Context: After requirements are detailed user: 'Let me design the screens' assistant: 'I will use designing-wireframes skill' <commentary>Triggered by screen design request</commentary></example>
Consistent style guide for writing blog posts about projects and technical work. Supports quick updates, detailed write-ups, retrospectives, and tutorials. Designed for low-friction entry and easy scanning.
[Task Mgmt] A Skill that adds new tasks with priority tags to Docs/Task/{StepName}_Task.md documents for multi-agent parallel development. AI agent MUST invoke this skill AUTOMATICALLY when (1) discovering new work items during implementation, (2) user requests a new feature/fix, (3) breaking down a large task into subtasks, (4) identifying follow-up work after completing a task. CRITICAL - Never modify document structure, only add tasks with proper priority tags (!high, !medium, !low). Tasks should be distributed to avoid file conflicts between workers. (user)
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.
