strategic-proposallisted

Spawn 5 domain experts to propose roadmap items, then an AI council drafts a roadmap, a Strategic Critic challenges it, and the council finalizes with revisions. Updates the pinned roadmap issue and /roadmap page data. TRIGGER when: asked to build roadmap, prioritize features, strategic proposal, "what should we build next", or rank product priorities.
mifunedev/openharness · ★ 38 · AI & Automation · score 80

Install: claude install-skill mifunedev/openharness

# Strategic Proposal Spawn 5 specialized expert sub-agents in parallel, each proposing roadmap items from their domain. An Expert AI Council drafts the roadmap, a Strategic Critic challenges it with adversarial backpressure, and the Council finalizes with revisions. The result is published as a pinned GitHub issue and written to `docs/roadmap.md`. **Core principle: SIGNAL OVER FEATURES.** Items require evidence of user demand before entering "Build Now" phase. Infrastructure prerequisites are exempt. The Critic ensures the council isn't inflating signal or sandbagging complexity. ## Variant: V2MOM / strategic operating model → wiki plan Use this variant when the user asks for a council to define a V2MOM, operating model, strategic principles, or a plan to add strategic synthesis to the wiki. Do **not** force the full roadmap/GitHub-issue publishing flow unless the user explicitly asks for a roadmap update. 1. Gather current product truth from README/docs/context/wiki plus live external signal if available. 2. Spawn a small lens-diverse council (e.g. Product/Founder, Systems/Ops, Market/Docs) rather than the roadmap-specific five expert roles. 3. Run one adversarial Strategy Critic after the council draft. The critic must challenge overreach, weak measures, contradictions, and wiki-scope mistakes. 4. Final synthesis should separate: - **Council decision**: Vision, Values, Methods, Obstacles, Measures. - **Wiki plan**: exact target entry, draft frontmatter/body, veri