mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

[COORD-002] Implement issue parser agent #158

New Issue
Closed
opened 2026-01-31 21:27:55 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-31 21:27:55 +00:00
Owner
Copy Link

Objective

Create AI agent (Sonnet) that parses issue markdown body to extract structured metadata.

Implementation Details

  1. Create parse_issue_metadata() function
  2. Use Anthropic API with Sonnet model
  3. Extract: estimated_context, difficulty, assigned_agent, blocks, blocked_by
  4. Return structured JSON
  5. Handle parse failures gracefully (use defaults)
  6. Cache results to avoid re-parsing

Context Estimate

  • Files to modify: 3 (parser.py, agent.py, models.py)
  • Implementation complexity: medium (20000 tokens)
  • Test requirements: medium (10000 tokens)
  • Documentation: medium (3000 tokens)
  • Total estimated: 46800 tokens
  • Recommended agent: glm

Difficulty

medium

Dependencies

  • Blocked by: #157 (COORD-001 - needs webhook to trigger parser)
  • Blocks: COORD-003 (queue needs parsed metadata)

Acceptance Criteria

  • Parser extracts all required fields
  • Returns valid JSON matching schema
  • Handles missing fields with defaults
  • Caches parse results (avoid duplicate API calls)
  • 85% test coverage
  • Works with real issue bodies from COORD-XXX issues
  • Average parse time < 2 seconds

Testing Requirements

  • Unit tests with sample issue bodies
  • Test missing fields → defaults
  • Test malformed markdown → graceful failure
  • Integration test with real Anthropic API
  • Cost test: Track token usage per parse
## Objective Create AI agent (Sonnet) that parses issue markdown body to extract structured metadata. ## Implementation Details 1. Create parse_issue_metadata() function 2. Use Anthropic API with Sonnet model 3. Extract: estimated_context, difficulty, assigned_agent, blocks, blocked_by 4. Return structured JSON 5. Handle parse failures gracefully (use defaults) 6. Cache results to avoid re-parsing ## Context Estimate - Files to modify: 3 (parser.py, agent.py, models.py) - Implementation complexity: medium (20000 tokens) - Test requirements: medium (10000 tokens) - Documentation: medium (3000 tokens) - **Total estimated: 46800 tokens** - **Recommended agent: glm** ## Difficulty medium ## Dependencies - Blocked by: #157 (COORD-001 - needs webhook to trigger parser) - Blocks: COORD-003 (queue needs parsed metadata) ## Acceptance Criteria - [ ] Parser extracts all required fields - [ ] Returns valid JSON matching schema - [ ] Handles missing fields with defaults - [ ] Caches parse results (avoid duplicate API calls) - [ ] 85% test coverage - [ ] Works with real issue bodies from COORD-XXX issues - [ ] Average parse time < 2 seconds ## Testing Requirements - Unit tests with sample issue bodies - Test missing fields → defaults - Test malformed markdown → graceful failure - Integration test with real Anthropic API - Cost test: Track token usage per parse
jason.woltje added the aip0apiapi labels 2026-01-31 21:27:55 +00:00
jason.woltje added this to the M4.1-Coordinator (0.0.4) milestone 2026-01-31 21:28:43 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label ai api api p0
Milestone
No items
No Milestone M4.1-Coordinator (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#158
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?