القائمة
Generate OpenAPI specifications for story endpoints. Use when user wants to create API specs for a story or mentions /api-spec command.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review the latest work unit with fresh, unnarrowed eyes and surface any problem it contains as follow-ups. Use after a work-unit commit, or when the user runs /agent-review.
Continue working on a story or task by reading progress.md, executing the next work unit, and updating progress. Use when user wants to resume story/task work or mentions /continue command.
Run a Selenium test in visible (non-headless) mode with slowdown so the user can watch it. Use when user wants to demo or visually watch a Selenium test or mentions /demo command.
Preview the planned design for a scenario before writing tests. Shows domain model changes, usecase patterns, and key design choices. Use before red-usecase to get user approval on the implementation approach. If the user rejects the design, offers to discuss inline or escalate to /architecture for a full ADR.
Write a journey summary capturing noteworthy moments (predictions, decisions, surprises, mistakes, quirks). Runs automatically the moment the agent observes something worth noting during work, and manually before /clear or /compact as a final sweep. Idempotent — skips entries already recorded. Use when the agent observes a noteworthy moment, before clearing context, or when the user mentions /handoff.
Re-explain the last thing in plain words. Use ONLY when the user explicitly types /plain or asks to "explain that simply / in plain words / like I'm not an expert". Never invoke on your own initiative — this is a manual button the user presses when something was hard to follow.
| name | api-spec |
| description | Generate OpenAPI specifications for story endpoints. Use when user wants to create API specs for a story or mentions /api-spec command. |
Generate OpenAPI 3.0.3 specifications for frontend endpoints in a story.
/api-spec "Story name"
/api-spec 5 # By MVP story number
/api-spec # Interactive selection
Generate the MINIMUM viable API, not the complete API.
Read context files:
ProductSpecification/BriefProductDescription.txtProductSpecification/stories.mdProductSpecification/stories/*/mockups/ (UI mockups)ProductSpecification/stories/*/interview.md (if exists — authoritative source for API details)Parse user input to find target story (by name, number, or interactive)
Read story specification: ProductSpecification/stories/NN-story-name/NN_StoryName.md
Load .claude/templates/spec/api-spec-template.md for document formats.
Based on story and mockups, identify the minimum endpoints needed.
endpoints.md in story folderProductSpecification/api-specs/[resource]_[action].yamlReport: created files, endpoints generated, design decisions.
/api/v1/ prefix