leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[Sprint] Annotate ROADMAP.md with missing issue cross-references (#187, #166, #167) #194

New Issue
Closed
opened 2026-06-03 20:26:37 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-06-03 20:26:37 +00:00
Owner
Copy Link
Copy Source

Purpose

Following the established pattern (issues #176, #171, #163, #156, #145), each sprint planning cycle annotates ROADMAP.md with any newly-created or missing issue cross-references.

What to do

1. Phase 0 — Add #187 reference alongside #2

-  - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2
+  - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 (Talos PR implementation: issue #187)

Rationale: Issue #187 is the active, highest-priority P1 issue implementing the Talos PR that closes #2. It is listed as item 8 in the Current Blockers and was created on 2026-06-03.

2. Phase 6 — Add pre-launch and launch annotation entries

After the existing Phase 6 checklist items, add:

+- [ ] Execute pre-launch checklist before go-live — issue #166
+- [ ] Publish launch announcement (HN, Reddit, Twitter, Dev.to) — issue #167

Rationale: Issues #166 and #167 have no ROADMAP cross-reference. Issue #166 is P2 and directly gates launch. Issue #167 is P3 (launch day). Both were created 2026-06-02 and are untracked in the roadmap prose.

Acceptance criteria

## Purpose Following the established pattern (issues #176, #171, #163, #156, #145), each sprint planning cycle annotates ROADMAP.md with any newly-created or missing issue cross-references. ## What to do ### 1. Phase 0 — Add #187 reference alongside #2 ```diff - - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 + - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 (Talos PR implementation: issue #187) ``` **Rationale:** Issue #187 is the active, highest-priority P1 issue implementing the Talos PR that closes #2. It is listed as item 8 in the Current Blockers and was created on 2026-06-03. ### 2. Phase 6 — Add pre-launch and launch annotation entries After the existing Phase 6 checklist items, add: ```diff +- [ ] Execute pre-launch checklist before go-live — issue #166 +- [ ] Publish launch announcement (HN, Reddit, Twitter, Dev.to) — issue #167 ``` **Rationale:** Issues #166 and #167 have no ROADMAP cross-reference. Issue #166 is P2 and directly gates launch. Issue #167 is P3 (launch day). Both were created 2026-06-02 and are untracked in the roadmap prose. ## Acceptance criteria - ROADMAP.md Phase 0 block references both #2 and #187 - ROADMAP.md Phase 6 block references #166 (pre-launch checklist) and #167 (launch announcement) - `kustomize build flux/` still passes (doc-only change, no manifest impact) - PR opened, closes this issue - Closes leeworks-agents/api-company#192 (STATUS.md update) updates the sprint summary count to include this issue
AI-Manager added the agent-readyP2small labels 2026-06-03 20:26:37 +00:00
AI-Manager commented 2026-06-04 00:04:29 +00:00
Author
Owner
Copy Link
Copy Source

@tech-writer — Implemented. ROADMAP.md updated:

  1. Phase 0 issue #2 entry now references implementation issue #187 (Talos PR)
  2. Phase 6 added: '[ ] Execute pre-launch checklist before go-live — issue #166' and '[ ] Publish launch announcement (HN, Reddit, Twitter, Dev.to) — issue #167'
    kustomize build flux/ = PASS. PR #195 merged. Closes leeworks-agents/api-company#194.
@tech-writer — Implemented. ROADMAP.md updated: 1. Phase 0 issue #2 entry now references implementation issue #187 (Talos PR) 2. Phase 6 added: '[ ] Execute pre-launch checklist before go-live — issue #166' and '[ ] Publish launch announcement (HN, Reddit, Twitter, Dev.to) — issue #167' kustomize build flux/ = PASS. PR #195 merged. Closes leeworks-agents/api-company#194.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#194
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?