القائمة
Use when software work needs approach selection, scope boundaries, or a concrete design before planning or implementation.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/nilsclabb/yellowpages --skill yp-workflow-designيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Specialized review leaf for PR, branch, and diff review. Use from `yp-workflow-review` when the user explicitly wants PR-oriented review or merge-readiness analysis.
The yellowpages skill defines how agents should create, author, and package skills, structure skills for navigation, navigate between skills and documentation, document planning work, define agent personas, run and track multi-step workflows, track state across sessions, and accumulate cross-session learnings. Use this skill when: creating a new skill, scaffolding a skill, authoring or packaging a skill, updating an existing skill, designing skill navigation systems, deciding how to split skill content into sub-files, writing SKILL.md frontmatter or body, documenting planning work (implementation plans, task lists, walkthroughs), defining an agent persona or specialist role, building a step-file workflow, tracking workflow state or gate status, reading or writing session learnings, or navigating a large codebase or skillbase efficiently.
Use when starting a session with yellowpages; introduces progressive disclosure and routes the agent to the correct category router.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | yp-workflow-design |
| description | Use when software work needs approach selection, scope boundaries, or a concrete design before planning or implementation. |
Turn a framed request into the simplest sufficient design. This stage exists to make trade-offs explicit before code exists.
Do not jump from uncertainty straight into implementation. If design choices are still unresolved, settle them here first.
| When useful | Load |
|---|---|
| You need better delegation or design handoff patterns | yp-workflow-subagents |
| You want concise review checkpoints before planning | yp-workflow-review-loops |
Leave this stage only when:
Go to yp-workflow-plan.