Loading...
Loading...
Found 29 Skills
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"
Draft or update requirement documents under `codestable/requirements/` for the project — use **user stories + plain language** to describe a capability's "reason for existence, solution approach, and boundaries", so non-technical readers can quickly understand the highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or during the feature-design phase, it is found that there is no corresponding requirement for the capability to be implemented this time.
Requirements Analysis Assistant that converts vague requirements into structured documents. Supports two output formats: User Story suitable for agile development, and PRD (Product Requirements Document) suitable for complete function planning. Clarifies ambiguities through targeted questions.
Draft or update requirement documents under `easysdd/requirements/` for the project — describe a capability's "reason for existence, solution approach, and boundaries" using **user stories + plain language**, so non-technical readers can quickly grasp the key highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: when the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or when it is found during the feature-design phase that there is no corresponding requirement for the capability to be implemented this time.
The user will invoke this skill to help them write a PRD (Product Requirement Document).
Break requirements into epics and user stories. Use when the user says "create the epics and stories list"
Max - Senior Product Owner with 10+ years agile experience. Use when defining product vision, creating/prioritizing backlog, writing user stories with acceptance criteria, making scope decisions, validating features against business goals, or planning releases and sprints. Also responds to 'Max' or /max command.
Expert at detecting stories that are too big and applying splitting heuristics. Use when user describes work that seems large, mentions multiple features in one story, or needs help breaking down requirements. Detects linguistic red flags (and, or, manage, handle) and suggests concrete splitting strategies. Use when: - Story has obvious red flags: "and", "or", "manage", "handle", "including" - User describes multiple features bundled together - Story feels vague or too large - User asks "how to split this story" Do NOT use when: - Story is already small and focused (< 1 day work) - Feature needs layered analysis without obvious split points (use hamburger-method instead) - User asks HOW to implement (use micro-steps-coach instead)
Autonomous mobile dev subagent that implements a single user story from a PRD for Expo / React Native apps. Use when you need parallel, independent mobile implementation tasks — screens, native components, data fetching, navigation. Designed to run alongside other ralph-mobile instances. Receives a specific task ID and PRD path. Returns a structured completion signal. Does NOT commit or modify the PRD — those are handled by the documenter. Loads expo, building-native-ui, vercel-react-native-skills, native-data-fetching, and expo-dev-client skills automatically.
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing backlog.
Event Storming 기법을 사용하여 PlantUML 시퀀스 다이어그램을 작성하고 유저스토리 개발을 준비합니다. 기획 구체화 시 사용하세요.