analysis-revision

/analysis-revision — Structured Review Revision

Guides the user through a structured revision workflow for an analysis design that has received review comments. Reads review feedback via MCP, creates a persistent tracking file for per-comment progress, and helps address each comment through interactive dialogue.

When to Use

• Design status is revision_requested and review comments need to be addressed
• Resuming a previously interrupted revision session
• Systematically working through all reviewer feedback before re-submitting

When NOT to Use

• Creating a new design from scratch (-> /analysis-design)
• Recording reasoning during active analysis (-> /analysis-journal)
• Structured reflection and conclusion (-> /analysis-reflection)
• Design is not in revision_requested status

Workflow

Phase 1: Situation Assessment

1. If $ARGUMENTS contains a design ID (e.g., "FP-H01"), use it directly. Otherwise, call list_analysis_designs(status="revision_requested") and ask the user to select.

2. get_analysis_design(design_id) -- load the design.

3. Status check: If status != "revision_requested", display an error and exit:

   このデザイン ({design_id}) は revision_requested 状態ではない (現在: {status})。
   レビューで修正依頼が出た後にこのスキルを使おう。
   

4. get_review_comments(design_id) -- get all review batches.

5. Batch selection (important -- do NOT just pick the newest batch overall):

   • Filter the returned batches to only those where status_after == "revision_requested"
   • From the filtered set, pick the one with the newest created_at
   • This is the target batch for this revision session

6. If no qualifying batch found (all batches have status_after != "revision_requested"):

   revision_requested に対応するレビューバッチが見つからない。
   レビューが WebUI 経由で提出されているか確認しよう。
   

   Exit.

7. Display situation summary:

   -- Revision: {design_id} --
   Title: {title}
   Status: {status}
   Target batch: {batch.id} ({batch.created_at})
   Reviewer: {batch.reviewer}
   Comments: {len(batch.comments)} items