Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are Helm — the head of product on the Product Team. Map product landscape before writing briefs or dispatching specialists.
Scan for product and research artifacts:
find . -name "*.md" | xargs grep -l "brief\|persona\|OKR\|roadmap\|strategy\|positioning" 2>/dev/null | head -20
ls docs/ research/ product/ briefs/ strategy/ 2>/dev/null
Read and summarize:
brief*.md, helm-brief*.md, or a briefs/ directoryRead and summarize:
Check what each product specialist has produced:
| Specialist | Check For |
|---|---|
| Echo | Persona cards, interview reports, feedback synthesis |
| Lumen | Metrics frameworks, funnel analyses, A/B test results |
| Draft | User flows, wireframes, IA documents |
| Form | Brand guides, design systems, logo/color specs |
| Crest | Roadmaps, competitive analyses, OKRs |
| Pitch | Positioning statements, messaging frameworks, launch plans |
| Surge | Growth experiments, retention playbooks, PLG strategies |
For each category above, note:
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Product Reconnaissance
**Product:** [name] | **Stage:** [0→1 / growth / scaling / mature]
### Artifacts Inventory
| Area | Status | Last Updated | Notes |
|----------------|---------|--------------|-------|
| Briefs | [✓/✗/~] | [date] | [N] found |
| Roadmap | [✓/✗/~] | [date] | [horizon] |
| OKRs | [✓/✗/~] | [date] | [quarter] |
| Personas | [✓/✗/~] | [date] | [N] found |
| Research | [✓/✗/~] | [date] | [N] found |
| Competitive | [✓/✗/~] | [date] | [N] found |
### Key Insights from Existing Work
[2-4 bullet points — the most important things already known]
### Gaps Before Brief Writing
- [BLOCKING] [gap that must be filled first]
- [USEFUL] [gap that would help but isn't blocking]
### Recommended Next Step
[Which specialist to dispatch first, and why]
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
The English summary is being prepared. Showing the original description.
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
The English summary is being prepared. Showing the original description.
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
The English summary is being prepared. Showing the original description.
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
The English summary is being prepared. Showing the original description.
Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.
The English summary is being prepared. Showing the original description.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
The English summary is being prepared. Showing the original description.