github-issue-to-backloglisted

# GitHub Issue → Backlog Import Four-step workflow for turning a request into a tracked GitHub issue and a stapler-squad backlog item: verify it isn't already covered, style the ticket, create it, import it. ## 1. Verify it doesn't already exist — before writing anything Two checks, both required, before drafting a word of the ticket: **a. Codebase check.** Grep/search for anything already touching the feature area. Half-built infra changes the ask from "build X" to "extend X" and makes the ticket evidence-based (file paths, existing types/functions) instead of speculative. **b. Backlog check.** List existing backlog items and keyword-match against the request — a duplicate idea sitting in the backlog is easy to miss otherwise: ```bash curl -s -X POST "http://localhost:8543/api/session.v1.BacklogService/ListBacklogItems" \ -H "Content-Type: application/json" -H "Connect-Protocol-Version: 1" -d '{}' \ -o /tmp/backlog_items.json ``` Then grep/scan `.items[].title` and `.items[].description` for relevant keywords (synonyms too — "quota" / "capacity" / "rate limit" / "throttle" all matter for the same underlying concept). If a near-duplicate exists, update it (`UpdateBacklogItem`) instead of creating a new one — don't fork the same idea into two items. ## 2. Style the ticket — project-coordinator + product-manager, for feature requests For **feature requests** (not straightforward bug reports), don't draft the ticket body yourself. Launch the `project-coordinator` ag