Loading...
Loading...
Found 41 Skills
Documentation-driven project development workflow. Intelligently determines task types, executes existing plans or generates new plans using feature-dev. **Use Cases:** - Complete project documentation exists, need to execute development tasks - User specifies to execute a certain plan (e.g., "Execute plan 001") - User requests to develop new features (automatically uses feature-dev to generate plans) **Prerequisites:** - The project should already have a docs/ documentation structure (PRD, SAD, etc.) - For new projects, it is recommended to first use the project-docs-setup skill to create complete documentation - If plan formulation is needed, it is recommended to use the project-planning skill **Relationship with Other Skills:** - project-docs-setup: Creates project documentation structure - project-planning: Formulates development plans (requirement clarification + design discussion + plan writing) - project-workflow: Executes development plans + updates documentation - Recommended workflow: project-docs-setup → project-planning → project-workflow **Trigger Methods:** - "Execute plan 001" / "Continue 001-user-authentication" - "Start development" / "Execute plan" / "Continue last task"
Use when you have a spec or requirements for a multi-step task, before touching code
Invoke before any creative or architectural work — feature design, component creation, or behavioral changes. A streamlined brainstorming process optimized for fast, focused decision-making.
Handles GitHub issue resolution end-to-end for prompts like "solve #123", "lets solve #123", "work on #123", "work on https://github.com/owner/repo/issues/123", or by pasting a direct GitHub issue URL as the request. USE FOR: solve #123, continue work on issue #123, work on https://github.com/owner/repo/issues/123, paste a GitHub issue URL for implementation work. DO NOT USE FOR: issue drafting only, PR review only, or non-implementation research.
Clarify requirements before implementing. Use when serious doubts arise.
Analyze a GitHub issue and create a detailed technical specification
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
Serial collaborative planning with Plan Note - Multi-domain serial task generation, unified plan-note.md, conflict detection. No agent delegation.
Rapid implementation for small, low-risk, well-defined changes. Use when the task is narrow in scope, has clear acceptance criteria, and can be completed safely without a formal multi-phase plan.
Use when the user says "/plan-review", "plan review", or "PRD review" and provides a plan file path that needs critical review and iterative refinement with Codex.
Query and manage Linear issues, cycles, labels, documents, attachments, projects, and team workflows. Use when creating, updating, searching, or triaging Linear issues, managing sprints, checking project status, or running a standup summary.
Diagnose GitHub-driven agile workflow problems and guide feature branch development