skill physics research

Other Community

Skill notes

Context References

Reference (do not load eagerly): Path: .claude/context/formats/return-metadata-file.md - Metadata file schema Note: This skill is a thin wrapper with internal postflight. Context is loaded by the delegated agent.

Trigger Conditions

This skill activates when: Task type is "physics" Research involves dynamical systems, chaos theory, or physics formalization Domain context files are needed for physics foundations

Stage 1: Input Validation

Validate required inputs: task_number - Must be provided and exist in state.json focus_prompt - Optional focus for research direction

Stage 2: Preflight Status Update

Update task status to "researching" BEFORE invoking subagent.

Stage 3: Create Postflight Marker

Create the marker file to prevent premature termination.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@benbrastmckie · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Physics Research Skill

Thin wrapper that delegates physics formalization research to `physics-research-agent` subagent.

**IMPORTANT**: This skill implements the skill-internal postflight pattern. After the subagent returns, this skill handles all postflight operations (status update, artifact linking, git commit) before returning.

## Context References

Reference (do not load eagerly):
- Path: `.claude/context/formats/return-metadata-file.md` - Metadata file schema

Note: This skill is a thin wrapper with internal postflight. Context is loaded by the delegated agent.

## Trigger Conditions

This skill activates when:
- Task type is "physics"
- Research involves dynamical systems, chaos theory, or physics formalization
- Domain context files are needed for physics foundations

---

## Execution Flow

### Stage 1: Input Validation

Validate required inputs:
- `task_number` - Must be provided and exist in state.json
- `focus_prompt` - Optional focus for research direction

---

### Stage 2: Preflight Status Update

Update task status to "researching" BEFORE invoking subagent.

---

### Stage 3: Create Postflight Marker

Create the marker file to prevent premature termination.

---

### Stage 4: Prepare Delegation Context

Prepare delegation context for the subagent:

```json
{
  "session_id": "sess_{timestamp}_{random}",
  "delegation_depth": 1,
  "delegation_path": ["orchestrator", "research", "skill-physics-research"],
  "timeout": 3600,
  "task_context": {
    "task_number": N,
    "task_name": "{project_name}",
    "description": "{description}",
    "task_type": "physics"
  },
  "focus_prompt": "{optional focus}",
  "metadata_file_path": "specs/{NNN}_{SLUG}/.return-meta.json"
}
```

---

### Stage 5: Invoke Subagent

**CRITICAL**: You MUST use the **Agent** tool to spawn the subagent.

**Required Tool Invocation**:
```
Tool: Agent (NOT Skill, NOT Plan)
Parameters:
  - subagent_type: "physics-research-agent"
  - prompt: [Include task_context, delegation_context, focus_prompt, metadata_file_path]
  - description: "Execute physics research for task {N}"
```

**DO NOT** use `Skill(physics-research-agent)` - this will FAIL.

The subagent will:
- Load domain context files from `.claude/context/project/physics/`
- Search codebase for existing patterns
- Use Mathlib lookup tools
- Execute web research for physics/dynamical systems literature
- Create research report in `specs/{NNN}_{SLUG}/reports/`
- Write metadata to `specs/{NNN}_{SLUG}/.return-meta.json`
- Return a brief text summary (NOT JSON)

---

### Stage 5b: Self-Execution Fallback

**CRITICAL**: If you performed the work above WITHOUT using the Agent tool (i.e., you read files,
wrote artifacts, or updated metadata directly instead of spawning a subagent), you MUST write a
`.return-meta.json` file now before proceeding to postflight. Use the schema from
`return-metadata-file.md` with status value "researched".

If you DID use the Agent tool, skip this stage -- the subagent already wrote the metadata.

---

## Postflight (ALWAYS EXECUTE)

The following stages MUST execute after work is complete, whether the work was done by a
subagent or inline (Stage 5b). Do NOT skip these stages for any reason.

### Stage 6-11: Standard Postflight

Parse metadata file, update task status, link artifacts (update TODO.md per `@.claude/context/patterns/artifact-linking-todo.md` with `field_name=**Research**`, `next_field=**Plan**`), git commit, cleanup, return brief summary.

---

## Error Handling

Standard error handling patterns: validate inputs, handle missing metadata, non-blocking git failures.

---

## Return Format

This skill returns a **brief text summary** (NOT JSON). The JSON metadata is written to the file and processed internally.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.