القائمة
Use when the user has a rough product or feature idea and wants it expanded into user stories, workflows, open questions, and implementation considerations.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Brainstorming specialist. Use before implementing any feature, fix or cli design to discuss the approach with the user first. Plans data models, storage layouts, test scenarios, and expected outputs.
OpenAI-compatible HTTP mock server for testing agents without real LLM calls. Loads a JSON config of request→response exchanges and returns pre-configured responses. Use when writing doctests or integration tests for agent runners.
Run human-style scenario verification after an agent claims work is done: git status, build into ~/.sandbox/bin, sandbox HOME=~/.sandbox/default-home, real integration/E2E scenarios (start servers, browser-agent for UI), always-labeled depth, markdown transcript written and inlined for review. Use for "verify on my behalf", before commit. Complements doctests; does not replace them. Load a sub-topic with: agent-pro skill --show verify-on-behalf-of-user/<topic>
Break a large implementation plan into dependency-ordered phases that are independently implementable and verifiable. Use when the user runs /split-phases, or says "split into phases", "phase this plan", "break into units of work", "dependency-ordered milestones", or wants a giant plan split for phase-by-phase work.
Meta-skill: distill durable high-signal guidance (worked vs failed, wrong → correct, and anything else that quickens future similar tasks) into a brief reusable skill document with YAML frontmatter. When the user does not explicitly ask for a new skill/file, prefer updating an existing skill over creating one. Writes skills/<name>/SKILL.md (or docs|doc/skills/…). Use for /summarize-a-skill, "summarize what worked", "lessons learned into a skill", or "write a skill from this session".
Intent router that classifies user input and delegates to the appropriate specialist agent or skill. Use this for any initial user message to determine the right next step before diving in.
| name | idea-expander |
| description | Use when the user has a rough product or feature idea and wants it expanded into user stories, workflows, open questions, and implementation considerations. |
Expand a feature idea into a comprehensive plan. Follow these steps:
Brainstorm — Expand the idea considering core functionality, user roles, integration points, error states, technical constraints, and UI/UX.
Clarify — If details are ambiguous, batch all questions and call
add-pending-questions with JSON arguments. Each argument has a question
field and optional options array. After calling it, stop and wait for
answers. Only ask questions that affect feature design or implementation.
Write the Expansion — Produce a comprehensive expansion with these sections: Overview, User Stories, User Flows, Functional Requirements, Non-Functional Requirements, Edge Cases & Error Handling, Technical Considerations, and Open Questions. Be specific and concrete.
Output to a markdown file with an auto-derived UPPER_CASE slug name (e.g.
FEATURE-IDEA.md). The report must include the original idea, all
clarifications and answers, and all sections.
