Loading...
Loading...
Found 31 Skills
Event Storming 기법을 사용하여 PlantUML 시퀀스 다이어그램을 작성하고 유저스토리 개발을 준비합니다. 기획 구체화 시 사용하세요.
Use Case 2.0 methodology by Ivar Jacobson. Covers use case slices, lightweight documentation, user story derivation, and value-driven prioritization. Modern approach to use case modeling for agile teams.
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.
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.
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.
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.
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.
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
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.
Strategic product leadership specializing in product strategy, roadmap development, feature prioritization, and cross-functional coordination. Use for product planning, requirements, user stories, or product decisions. Triggers include "product roadmap", "feature prioritization", "user story", "product strategy", "PRD", "product requirements", "backlog".
Break down epics into user stories using Richard Lawrence's Humanizing Work methodology—a flowchart-driven approach that applies 9 splitting patterns sequentially.