Menu
Research-driven positioning exercise — competitive research, guided framework application, and positioning document generation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Backlog-scale orchestration on top of /workflow — drives PM items through refine → plan → implement → review → local-merge via role-specialized sub-agents dispatched in parallel waves, each item isolated in its own git worktree. Bare /swarm summarizes state; /swarm <goal> runs the orchestrator; /swarm:setup sets up the charter and .agent-tools/ umbrella; /swarm:continue resumes a paused run.
Capture durable knowledge from any engineering work — debugging solutions, refactors, features, design decisions, reusable patterns — and maintain memory quality so each unit of work compounds the next
Principal workflow entry — resolve portfolio mode (swarm resume/handoff or unit state machine), drive work without inventing path; hard-stop when path is not established
Initialize and maintain planning root (.agent-tools/planning preferred), conventions (tracks, gates, integration), runs ledger scaffold, and shared memory under .agent-tools/memory/ (AGENTS.md memory-link) for the workflow family.
Parent skill for the workflow family — principal session entry is /workflow:continue (also bare /workflow). Horizon mapping, brainstorm, refine, plan, execute, review, audit, compound. Vertical-slice and deliverable-partition modes.
Detect gaps in the canonical skill corpus, propose targeted improvements, validate changes, and present for review. Inventories src/** skill trees; optional run-ledger seeds for process IP gaps.
| name | product:position |
| description | Research-driven positioning exercise — competitive research, guided framework application, and positioning document generation |
| argument-hint | ['.', directory path, or 'continue'] |
| user-invocable | true |
References: @product
Research-driven positioning exercise producing ./planning/positioning.md (April Dunford framework + competitive research). Not a template fill-in — research first, then guided decisions.
$ARGUMENTS
| Input Pattern | Scope | Action |
|---|---|---|
. or empty | Current project | Full positioning from scratch |
| Directory path | Target project | Position that project |
continue | Resume | Continue from ./planning/positioning.md |
--from-audit | Post-audit | Start from recent /product:audit report |
Read README hero, landing page, package metadata, existing ./planning/ positioning, docs intro.
Extract current claims: what / who / problem.
Spawn 3 parallel research agents:
Return structured profiles with citations.
Present findings using templates/discovery-summary.md (load and fill).
For each Dunford step: present research evidence; user decides.
Write ./planning/positioning.md using templates/positioning-doc.md (load and fill from decisions + research sources + last_research date).
/product:audit — assess gaps then re-audit after positioning/product:brief — content generation from positioning doc/workflow:plan — feature gaps from claims vs codebase/workflow:compound — capture competitive research findings