[UX/RFC] Redesign AssemblyMCP tool experience using KoreaLawMCP patterns

[StatPan]

Purpose

Track the KoreaLawMCP-inspired UX redesign for AssemblyMCP.

This issue is the public roadmap/index. Detailed PRD-style notes should not be committed to the repository as long-lived docs until the public tool contract is accepted. Work should proceed through focused Gira/GitHub issues.

Reference: https://github.com/chrisryugj/korean-law-mcp
Related: #48

Direction

AssemblyMCP should evolve from a flat API wrapper surface into a workflow-oriented legislative research MCP.

Key principles adapted from KoreaLawMCP:

• Keep the public MCP surface compact and user-job oriented.
• Prefer workflow tools over adding many raw wrappers.
• Keep raw API discovery as an explicit fallback path.
• Add machine-readable failure markers so LLM clients do not fabricate answers when official data is missing.
• Treat README/onboarding as part of the product UX, but update it only after the public contract stabilizes.

Roadmap Issues

1. [UX] Define public tool surface and naming contract #62 - Define public tool surface and naming contract
2. [UX] Add machine-readable MCP failure markers #63 - Add machine-readable MCP failure markers
3. [UX] Implement legislative claim verification #64 - Implement legislative claim verification
4. [UX] Implement issue_brief workflow #65 - Implement issue_brief workflow
5. [UX] Normalize bill_timeline workflow #66 - Normalize bill_timeline workflow
6. [UX] Design legislative_impact_map relation workflow #67 - Design legislative_impact_map relation workflow
7. [UX] Implement watch_action_plan monitoring workflow #68 - Implement watch_action_plan monitoring workflow
8. [Docs] Rewrite README around workflow-first MCP UX #69 - Rewrite README around workflow-first MCP UX

Suggested Order

1. Finish [UX] Define public tool surface and naming contract #62 first. This decides the public contract and relationship to [RFC] MCP 도구 계층 재구조화 및 네이밍 컨벤션 정립 #48.
2. Implement [UX] Add machine-readable MCP failure markers #63 before workflow tools so all new tools share failure semantics.
3. Implement [UX] Implement legislative claim verification #64 and [UX] Implement issue_brief workflow #65 as the first functional UX slice.
4. Add [UX] Normalize bill_timeline workflow #66, [UX] Design legislative_impact_map relation workflow #67, and [UX] Implement watch_action_plan monitoring workflow #68 after the first workflow contract has settled.
5. Finish [Docs] Rewrite README around workflow-first MCP UX #69 last so documentation matches actual released tools.

Notes

A draft planning PR (#61) was intentionally closed because the PRD-style plan should be converted into issue-sized work rather than committed directly into the open-source repository.

[StatPan]

Progress Update

Created initial Phase 0 planning artifacts for the KoreaLawMCP-inspired UX redesign.

Files changed:

• docs/UX_REDESIGN_PLAN.md: current tool surface audit, target UX model, proposed workflow tools, failure marker contract, compatibility plan, and phased implementation plan.
• docs/PROJECT_STATUS.md: updated current branch, issue link, verified test count, and next steps for [UX/RFC] Redesign AssemblyMCP tool experience using KoreaLawMCP patterns #60.

Verification:

• uv run --frozen ruff check . -> passed
• uv run --frozen pytest -q -> 68 passed

No public MCP tool contract or runtime code changed in this step.

Context:

• Ticket: [UX/RFC] Redesign AssemblyMCP tool experience using KoreaLawMCP patterns #60
• Status: In progress
• Linked PR: none
• Blockers: missing_linked_pr
• Next: gira ticket pr --repo StatPan/AssemblyMCP --ticket 60 --apply