القائمة
Format a GitHub (or GitLab) issue Summary for the feature-planner and later phases after gh issue view.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Preserve project architecture and SOLID when proposing or writing code. Always identify the correct layer and minimal design first.
Explore and shape a new feature before code generation. Always determine architectural placement, design options, trade-offs, and recommended approach first.
Diagnose runtime and launch issues that happen only on physical iPhone devices. Always plan first, then wait for approval before changing code.
Diagnose and repair Kotlin Multiplatform + Swift build failures. Always plan first, wait for confirmation, then apply minimal fixes.
Structure a manual feature or bug report before feature-planner when not starting from a GitLab issue.
Checklist for merge request title and description before release-manager creates the MR.
| name | workflow-issue-handoff |
| description | Format a GitHub (or GitLab) issue Summary for the feature-planner and later phases after gh issue view. |
Use after fetching an issue. Produce a single structured block the user can approve before planning.
Primary (GitHub):
gh issue view <n> --repo <owner/repo>
Secondary (GitLab, if applicable):
glab issue view <n>
Fill every section in the template. Do not implement code in this skill—summary only.