Time-boxed throwaway investigation to answer one hard question. Use when facing technical uncertainty before committing to a frontier item or scoped slice — the output is knowledge, not production code.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Retire one uncertainty. Output is knowledge, not code — spike code is throwaway, never promoted directly (Beck, XP). One question per spike; if multiple unknowns exist, run multiple spikes.
Spike notes are temporary. Reconcile durable findings into memory/SPEC.md and memory/PLAN.md instead of inventing standalone investigation docs unless the user explicitly asks for one.
The question and approach: $ARGUMENTS
## Question
[The question]
## Approach
[What was tried]
## Verdict
[Answer: yes/no/partially, with evidence]
## Recommendation
[Proceed with ln-scope, try a different approach, or abandon]
After the verdict, do all of these before presenting routing options:
done in memory/PLAN.md if the spike itself was tracked as a frontier item, or update the affected frontier definition if it was a proving step inside a frontiermemory/SPEC.md §Assumptions — set Status to validated or invalidated as evidence warrants, update Confidence if the evidence changed it, and flag implicated frontier items in memory/PLAN.mdmemory/SPEC.md §Decisions, new assumptions to §Assumptionsmemory/PLAN.mdThese are bookkeeping steps, not optional. Routing comes after.
After traceability is complete, present these options to the user (use tool-ask-question):
| # | Label | Target | Why |
|---|---|---|---|
| 1 | Scope a slice | ln-scope | Question answered — ready to define the next scoped slice |
| 2 | Spike again | ln-spike | New question emerged, needs another investigation |
| 3 | Revise spec | ln-spec | Verdict revealed the spec needs structural revision |
| 4 | Revise plan | ln-plan | Verdict changes what frontier items or slices are needed |
| 5 | Back to triage | ln-consult | Verdict changes the overall direction |
Recommended: 1 if the spike validated. If it invalidated an architectural or requirement-level assumption, prefer 3; if it mainly changes frontier/slice feasibility, ordering, or dependencies, prefer 4.
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.
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
The English summary is being prepared. Showing the original description.
Search the live web via Perplexity Search API. Use when you need current documentation, release notes, vendor pages, news, domain-constrained web search, or date/recency filtering. Not for local codebase search or stable docs already in context.
The English summary is being prepared. Showing the original description.
Chrome DevTools CLI for browser automation via shell commands. Use when interacting with web pages from the command line — navigating, clicking, filling forms, inspecting console/network, taking screenshots, or extracting page content. Triggers on: browse a page, automate Chrome, inspect console, check network requests, take a screenshot, fill a form, click a button.
The English summary is being prepared. Showing the original description.
Uses the chrome-devtools-axi CLI for browser automation, accessibility-tree snapshots, console and network inspection, screenshots, Lighthouse audits, and performance traces. Use when interacting with Chrome from the shell, especially when the user mentions chrome-devtools-axi, AX snapshots, browser debugging, or DevTools automation from the command line.
The English summary is being prepared. Showing the original description.
Deep expertise in cmux — the terminal multiplexer with native browser views. Use when managing panes, reading terminal output, sending keystrokes, opening browser views, or manually testing web UIs and TUIs inside cmux. Triggers on: cmux, open a browser pane, split terminal, read screen, send keys, test this UI in cmux, preview in cmux.
The English summary is being prepared. Showing the original description.
Uses the gh-axi CLI for GitHub shell operations: issue, pull request, workflow run, release, repo, search, and API tasks. Prefer this over regular `gh` for GitHub reads and simple mutations when an agent needs compact, structured, suggestion-rich output. Triggers on: gh, GitHub CLI, github issue, github pr, pull request, workflow run, github release, gh api, repo inspection, list PRs, view issue, check workflow runs, inspect repo, GitHub shell operations.
The English summary is being prepared. Showing the original description.