跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

reconnaissance

Use when beginning a new heist — deploys associates to survey the target codebase, existing tests, dependencies, documentation, and the ledger to produce a reconnaissance dossier for the don's review

kucherenko · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add kucherenko/gangsta --skill reconnaissance

技能说明


name: reconnaissance description: Use when beginning a new heist — deploys associates to survey the target codebase, existing tests, dependencies, documentation, and the ledger to produce a reconnaissance dossier for the don's review

Reconnaissance: Intel and Environment Mapping

Overview

Every Heist begins with gathering intel. The Underboss deploys Associates to perform a detailed survey of the target codebase and infrastructure. The output is a Reconnaissance Dossier that informs all subsequent phases.

Trigger

Invoked when the Don expresses building or creative intent.

Process

Step 1: Analyze Intent

The Underboss parses the Don's request to identify:

  • Objective: What is being built or changed?
  • Scope: Which parts of the system are affected?
  • Constraints: Any explicit requirements or limitations?

Step 2: Deploy Associates

Dispatch Associate subagents in parallel to gather intel.

Subagent type: Use subagent_type: "associate" for all Associate dispatches. Do NOT use "general" or "general-purpose" — these are not valid in a Gangsta installation.

Greenfield Mode (empty or near-empty workspace)

Before dispatching the standard survey, count the files in the working directory (excluding .git, docs/gangsta/, and other meta directories).

Trigger: the workspace contains fewer than 5 source files OR no recognizable project manifest (package.json, requirements.txt, go.mod, Cargo.toml, pyproject.toml, etc.).

When the trigger fires, the reconnaissance objective shifts from "survey the existing code" to "sharpen the IDEA". The standard codebase survey is still run (to capture what little exists), but it is no longer the center. Instead, deploy these associates in parallel:

Associate TaskWhat to Investigate
Idea FramingRestate the Don's objective in the Don's own words. Identify the problem being solved, who has it, and what evidence (if any) the Don offered. Surface hidden assumptions.
AnaloguesSearch the internet for existing tools, libraries, products, or papers that solve the same or adjacent problems. For each analogue: name, what it does, what it gets right, what it gets wrong, license/hosting model. Use the webfetch tool. Produce at least 3 analogues; if fewer than 3 exist, say so and explain why the space is sparse.
Prior Art & PatternsSearch the internet for relevant prior art: protocols, data formats, algorithms, design patterns, prior attempts, postmortems. Cite sources (URLs).
Constraint & Risk SurveyEnumerate known constraints for the domain: performance ceilings, security concerns, regulatory, accessibility, platform limits. Cite sources.
Codebase Structure(Standard survey — what little exists in the workspace.)
Ledger Search(Standard survey.)
Constitution(Standard survey.)

The Dossier's Codebase Overview section becomes a thin note describing the empty/near-empty state. The bulk of the Dossier moves to new sections — see the Greenfield Dossier Format below.

Greenfield Dossier Format (replaces the standard format when greenfield mode fires):

---
heist: <heist-name>
date: YYYY-MM-DD
status: pending-review
mode: greenfield
---

# Reconnaissance Dossier: <Heist Name>

## Objective
<What the Don wants to build — restated in Don's words, plus interpreted objective>

## Workspace State
<One paragraph: what currently exists. If empty, say "empty workspace — greenfield".>

## Idea Framing
- Problem: <the actual problem>
- Who has it: <audience>
- Evidence: <what the Don offered; if none, say "no evidence offered — to be grilled">
- Hidden assumptions:
  - <assumption> — risk if wrong: HIGH/MEDIUM/LOW

## Analogues
| Name | What it does | Strengths | Weaknesses | License/Hosting |
|------|--------------|-----------|-----------|-----------------|
| ... | ... | ... | ... | ... |

## Prior Art & Patterns
- <pattern / protocol / algorithm> — <URL> — relevance: <how it applies>

## Constraint & Risk Survey
- <constraint> — source: <URL>

## Existing Test Coverage
<Near-empty in greenfield mode — note what, if anything, exists.>

## Dependencies
<Near-empty in greenfield mode — list any the Don named.>

## Relevant Ledger Entries
### Applicable Insights
- <insight reference + summary>
### Applicable Negative Constraints
- NEVER <constraint> — Source: fails/YYYY-MM-DD-<topic>.md

## Risks and Unknowns
<Domain risks surfaced by the Constraint & Risk Survey; unknowns the analogues search could not resolve.>

## Recommended Scope
<Suggested boundaries — since there is no codebase to constrain scope, scope is the IDEA's own bounds: which analogue features to adopt, which to reject, which sub-problems are in/out.>

The Don reviews this dossier the same way. The proceed menu (Step 4) is unchanged.

Standard Mode (existing codebase)

When the workspace contains a real codebase (5+ source files OR a recognizable project manifest), run the standard survey below.

Associate TaskWhat to Survey
Codebase StructureFile tree, key directories, framework detection, entry points
Existing TestsTest files, coverage areas, test framework, passing/failing status
Dependenciespackage.json / requirements.txt / go.mod etc., versions, known issues
DocumentationREADME, existing specs, API docs, inline documentation
Ledger SearchSearch docs/gangsta/insights/ and docs/gangsta/fails/ for entries with tags matching the objective
ConstitutionRead docs/gangsta/constitution.md for applicable Commandments and Negative Constraints

Step 3: Synthesize Dossier

Compile Associate reports into a structured Reconnaissance Dossier.

Dossier Format (Standard Mode)

Save to: docs/gangsta/<heist-name>/recon/YYYY-MM-DD-recon-dossier.md

In greenfield mode, use the Greenfield Dossier Format defined above instead.

---
heist: <heis
阅读完整来源 ↗