forge-clarifylisted

# Forge Clarify This is the step between triage and plan: `confirmed → clarified`. Its job is to validate understanding — reproduce bugs in a live environment, verify UX expectations for features, and capture visual evidence. This prevents the plan step from targeting the wrong code path or misunderstanding the desired outcome. Simple issues are auto-skipped (the lifecycle hook advances them to `clarified` without running this skill). ## Usage ``` /forge-clarify <documentId> ``` ## Tools - **forge_issues** — get/update issues - **forge_comments** — list/create comments - **Browser** — `mcp__claude-in-chrome__*` tools (navigate, click, type, screenshot) for live environment testing - **WebFetch** — for API endpoint testing ## Workflow ### Step 1: Fetch Issue & Triage Context Fetch the issue and its comments in parallel: ``` forge_issues → get → { documentId: "<id>" } forge_comments → list → { filters: { issue: "<documentId>" } } ``` Find the triage comment (starts with `**Triage**` by Snorlax) and extract **complexity** and **category**. Note: Simple issues are auto-skipped by the pipeline lifecycle — they never reach this skill. This skill only runs for Medium and Complex issues. ### Step 2: Resolve Live Environment Determine where to test: 1. Issue's `previewUrl` / `previewApiUrl` (if a preview deployment exists) 2. Project's staging URLs from `forge_config → get` (previewDeploy.stagingUrl / stagingApiUrl) 3. If none available → skip browser testing, note in c