Loading...
Loading...
Found 2,897 Skills
Interview the user and write a PRD for Ralph in .prd/prd-<feature>.md.
End-of-session reflection. Extracts memories, suggests updates to about-taylor.md and CLAUDE.md. Run before ending a long session or when context is getting full. Triggers on "debrief", "extract memories", "session summary".
This skill should be used when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Implements Manus-style file-based planning with task_plan.md, findings.md, and progress.md.
Learn unfamiliar implementation patterns and fill in missing pieces when building features in a specific environment (e.g., data fetching in a particular runtime). Use when you need to discover or confirm patterns for an unimplemented area; implementation uses erudita and osgrep.
This skill should be used when the user asks to write, edit, review, or improve Markdown content (README, docs, changelog, guides), or needs Markdown formatting, syntax help, or advanced patterns (tables, callouts, task lists, mermaid, details/summary, footnotes).
Iteratively write academic documents (paper sections, research proposals, technical documents) with quality improvement loop. Uses academic-planner for structure design and academic-reviewer for quality evaluation. Ensures no hallucinations through fact verification.
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
Generate structured product and technical documents through guided discovery. 8 document types: PRD, Brief, Issue, Task, User Story, RFC, ADR, TDD. Use when: defining products, reporting bugs, planning sprints, writing stories, proposing changes, recording decisions, designing systems. Triggers on "create PRD", "create issue", "report bug", "feature request", "create task", "create user story", "create RFC", "create ADR", "create TDD", "create document", "write doc".
Design system architecture and high-level technical strategy
Document debugging sessions with hypothesis tracking and knowledge base
Convert ambiguous user requests into structured USDM requirements documents. Decomposes requirements into Requirement → Reason → Description → Specification hierarchy. Integrates with GitHub Issues, Asana, and Jira tickets as input sources. Use when: "create requirements", "write requirements document", "USDM", "decompose requirements", "requirements definition", "要件定義", "要件を整理", "要件分解".
Conducts comprehensive 90-minute discovery interviews to extract complete product requirements before implementation. Triggers when starting new SaaS projects, defining product scope, or validating ideas. Includes product management expertise to guide users through difficult questions.