Automatically activate when user requests feature implementation, refactoring, or multi-step development tasks. Implements adaptive two-phase planning from ADR 0008 with per-task re-assessment and approval checkpoints.
Analyze multiple JIRA tickets in batch and provide comprehensive triage recommendations
General overview of instructions to the project
Analyze and improve Marp markdown presentations using SlideGauge. Use when working with Marp slides, presentation files ending in .md with marp frontmatter, or when user asks to check, analyze, improve, or validate slide quality. Requires slidegauge package (installed via uvx).
เกณฑ์ที่ชัดเจนว่า "งานเสร็จ" หมายความว่าอย่างไร ครอบคลุมทุก task type พร้อม checklist และ verification
Full 9-phase workflow for complex features, epics, and security-critical changes (2-4 hours)
Skill for analyzing ticket complexity and determining required workflow phases. Uses scoring system to classify tickets as SIMPLE, MEDIUM, or COMPLEX, which determines exploration depth and planning approach.
Show project detail. Requires authentication. Use for project management operations
Use when creating implementation plans, breaking down tasks, sequencing changes, planning TDD cycles, or creating a roadmap for implementing a user story.
Fetches a Linear issue and creates a comprehensive plan for implementation.
This skill should be used when the user asks to "view pipeline", "show hiring funnel", "candidate pipeline", "recruiting stages", "move candidate", or wants to view and manage the recruiting pipeline for a job in Ashby.
Orchestre cycle de vie modules (planification, exécution, finalisation), génère rapports professionnels, met à jour RAPPORT_GENERAL
Use this skill after a ralph-code phase has completed but before marking the task as complete in SCOPES.yml
Use when generating project roadmap - creates ROADMAP.md with milestones and timeline
Generate status reports for design documentation. Use when creating documentation summaries, tracking progress, or preparing documentation reviews.
ELD（Evidence-Loop Development）のPredict（予測）フェーズスキル。 変更の影響を因果タイプで分類し、段階化戦略と停止条件を確定する。 「賢く動く」よりも「壊さずに収束する」を優先。 使用タイミング: (1) 実装前の影響分析、(2) 「影響予測して」「段階化計画を立てて」、 (3) Phase 2: Designで変更計画を策定する時、(4) 複雑な変更前のリスク評価
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Analyze a feature request and advise on the best Ralph approach for extending an existing Ralph-built application. Use when planning new features, considering enhancements, or deciding how to add functionality. Triggers on: ralph enhance, extend ralph app, add feature to ralph project, how should I add, plan enhancement, enhance this app.
10 pre-dev workflow skills + 3 research agents organized into Small Track (4 gates, <2 days) and Large Track (9 gates, 2+ days) for systematic feature planning with research-first approach.
Reviews feature specifications for completeness, testability, and implementation readiness. Validates acceptance criteria, edge cases, and technical constraints. Use when reviewing feature specs before implementation or during sprint planning.
