packages/forge/src/skills/discovery-phase/SKILL.md
Use for structured exploration before committing to a plan — "I don't know where to start", "what are our options", "investigate", "research this", "explore options", "discovery". Ideal when requirements are unclear, entering a new domain, or facing architectural decisions. Produces a discovery document with options, tradeoffs, and a recommendation.
npx skillsauth add adrozdenko/soleri discovery-phaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structured exploration before committing to a plan. Define the question, research prior art, explore the codebase, identify constraints, draft options with tradeoffs, and recommend a path forward.
<HARD-GATE> Do NOT create a plan, write code, or take any implementation action until the discovery document is complete and the user has reviewed it. Discovery produces knowledge, not artifacts. </HARD-GATE>YOUR_AGENT_core op:search_intelligent params: { query: "<question>", mode: "scan" }. Also op:memory_search with crossProject: true.For each option:
| Field | Content | | ------------ | -------------------- | | Approach | One-sentence summary | | Pros | What it gives us | | Cons | What it costs | | Risk | What could go wrong | | Effort | S / M / L |
YOUR_AGENT_core op:capture_knowledge
params: {
title: "<topic> — discovery finding",
description: "<question, options considered, recommendation, rationale>",
type: "decision",
category: "<domain>",
tags: ["discovery", "decision"]
}
Save to docs/discoveries/YYYY-MM-DD-<topic>.md and commit. Then transition to the next skill.
| Op | When to Use |
| -------------------- | ---------------------------------- |
| search_intelligent | Search vault for prior art |
| memory_search | Check session history and projects |
| capture_knowledge | Persist discovery finding |
| route_intent | Classify what comes after |
testing
Triggers: "terse mode", "be brief", "less tokens", "fewer tokens", "compress output", "caveman", or invokes /terse. Token-efficient responses with full technical accuracy.
tools
Triggers: "compress this file", "compress CLAUDE.md", "compress memory", "shrink this", "reduce tokens in file", or invokes /compress. Compresses natural language files to save input tokens.
testing
Triggers: "release", "bump version", "publish packages", "cut a release", "version bump", "npm publish". Bumps monorepo versions, commits, tags, pushes to trigger CI release. Use deliver-and-ship for quality gates.
development
Triggers: "implement X", "build Y", "fix Z", "add feature", or any work task needing planning + execution. Full orchestration loop: plan, execute, complete with vault context and brain recs.