Get the FREE Ultimate OpenClaw Setup Guide →

Project Field Explorer

npx machina-cli add skill Vit0lze/Project-Evolver-Framework/project-field-explorer --openclaw
Files (1)
SKILL.md
2.2 KB

Project Field Explorer

This skill performs a constant, deep-dive research into every structural flaw identifying in GLOBAL_MAP.md. It prepares a fail-proof execution plan for future injection.

1. Trigger & Setup

Trigger: "Use the project-field-explorer skill to investigate the Breaking Points identified in the Global Map."

Data Retrieval:

  1. Autonomously locate GLOBAL_MAP.md in the workspace root or brain/ folder.
  2. Read the Vision section of the map.
  3. Vision Alignment: Ensure all research prioritizes the stated Project Purpose and Evolution Goal.

2. Deep-Dive Execution Logic

For EACH Breaking Point identified in the Map, perform the following unrestricted analysis:

  1. Inspect Code: Read the actual source code around the reported BREAK point.
  2. Extract Golden Rules: Identify the hidden business logic that must remain invariant.

    "What business value is this messy code actually providing?"

  3. Blast Radius: Trace references to determine exactly which files will break if this changes.
  4. Architectural Fit: Consult references/architectural-solutions.md to select the best pattern (SOLID, Design Patterns) for the fix.

3. Connective Handshake

For every breaking point, generate a Connective Handshake:

  1. Solution ID: Assign a unique ID (e.g., SOL-AUTH-01).
  2. External Dependencies: Explicitly check and list if new libraries (npm, pip) are needed.
  3. Target Manifest: List every file path that the future 'Injector' skill will need to modify.

4. Output

Generate a report using assets/templates/FIELD_RESEARCH_REPORT.md for each major issue (or consolidated for related issues).

Constraint Checklist:

  • No Limits: Deep dive until clarity is absolute.
  • Explicit Deps: Never assume libraries exist. Check them.
  • English Only: All reports must be in English.

Source

git clone https://github.com/Vit0lze/Project-Evolver-Framework/blob/main/Skill Files/project-field-explorer/SKILL.mdView on GitHub

Overview

Project Field Explorer performs constant, in-depth research into structural flaws identified in GLOBAL_MAP.md. It analyzes each Breaking Point, extracts invariant business rules, and crafts a fail-proof execution plan (Connective Handshake) for a future Injector skill.

How This Skill Works

It autonomously locates GLOBAL_MAP.md in the workspace root or brain/; reads the Vision section and aligns with the Project Purpose and Evolution Goal. For every Breaking Point, it inspects the involved code, extracts Golden Rules that must remain invariant, traces the blast radius across files, and selects architectural patterns from references/architectural-solutions.md. It then generates a Connective Handshake with a unique Solution ID, external dependency checks, and a Target Manifest of files the future Injector will modify, finally producing a FIELD_RESEARCH_REPORT.md per major issue or consolidated related issues.

When to Use It

  • You want to investigate Breaking Points identified in the Global Map.
  • You plan complex refactors and need a structured, risk-aware approach.
  • You need a fail-proof execution plan (Connective Handshake) for a future Injector skill.
  • You want to verify architectural compatibility (SOLID patterns, design patterns) for fixes.
  • You need output documentation using assets/templates/FIELD_RESEARCH_REPORT.md.

Quick Start

  1. Step 1: Trigger the skill with 'Use the project-field-explorer skill to investigate the Breaking Points identified in the Global Map.'
  2. Step 2: Allow it to locate GLOBAL_MAP.md, read Vision, and confirm alignment with Project Purpose.
  3. Step 3: For each Breaking Point, review code, derive Golden Rules, determine blast radius, and generate Connective Handshake + FIELD_RESEARCH_REPORT.md.

Best Practices

  • Always locate and verify GLOBAL_MAP.md at the workspace root or brain/ folder before analysis.
  • Ensure Vision Alignment with the Project Purpose and Evolution Goal during research.
  • Explicitly list any external dependencies (libraries, tools) required by changes.
  • For each Breaking Point, clearly delineate the Blast Radius and affected files.
  • Produce FIELD_RESEARCH_REPORT.md reports per major issue, or consolidate related issues when appropriate.

Example Use Cases

  • Investigating a Breaking Point in a legacy auth module and drafting a safe refactor plan.
  • Planning a large-scale refactor of the data access layer with clear invariant rules.
  • Generating a Connective Handshake for a hypothetical Injector skill with SOL-AUTH-01 as an ID.
  • Mapping cross-file impact to ensure no hidden dependencies are overlooked.
  • Consolidating related issues into a single FIELD_RESEARCH_REPORT.md using the provided template.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers ↗