القائمة
Use when a task needs broad source understanding before planning or execution.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use only when the user explicitly allows bounded unattended execution of an approved Alloy task.
Use when encountering a bug, regression, failing command, or unexpected behavior before attempting a fix.
Use before planning when requirements are ambiguous, large, user-visible, or likely to cause rework unless decisions are locked.
Use when implementing an approved Alloy plan. Maintains progress.md, enforces TDD/debug discipline, and stops on blocked gates.
Use when turning context or a clear user request into an implementation-ready plan with acceptance criteria, files, commands, gates, risks, and handoff.
Automated end-to-end QA — read acceptance criteria (Azure DevOps or manual), generate Playwright test plan, execute with screenshots/video/GIF, produce acceptance report. Uses Playwright CLI for deterministic, reportable execution.
| name | alloy-map-codebase |
| description | Use when a task needs broad source understanding before planning or execution. |
Use this skill to produce a bounded source map for a task without burning the main session on repeated exploration.
Write:
.alloy/tasks/<task-id>/codebase-map.md
# <task-id>: Codebase Map
## Question
## Entry Points
- File:
- Why it matters:
## Data And Control Flow
## Contracts
- Runtime payloads:
- Generated files:
- Public APIs:
## Tests And Commands
## Risky Boundaries
## Recommended Plan Inputs
- Files likely in scope:
- Files to avoid:
- Verification commands:
Planner or Builder may ask a one-shot Explorer to gather this map. The request must include the task id, search scope, and expected return format. Explorer must not edit files.
Report map path, files inspected, important boundaries, commands discovered, and risks for planning.