trace

Engineering Community

Skill notes

When to Use

Trace HOW architectural decisions evolved Find WHEN a concept was introduced Understand WHY something was designed a certain way Build provenance chain for design decisions For knowledge artifact lineage (learnings, patterns, tiers), use /provenance instead.

Execution Steps

Given /trace <concept>:

Step 1: Classify Target Type

Determine what kind of provenance to trace:

Step 2a: Design Decision Tracing (Concepts)

Launch 4 parallel search agents (CASS, Handoff, Git, Research) and wait for all to complete. Backend: Agents use Task(subagent_type="Explore") which maps to task(subagent_type="explore") in OpenCode. See skills/shared/SKILL.md ("Runtime-Native Spawn Backend Selection") for the shared contract. Read references/discovery-patterns.md for agent definitions and prompts.

Step 2b: Git-Based Tracing (Commits/Refs)

Read references/discovery-patterns.md for git-based tracing commands.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
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
@diegosouzapw · 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.

01
Step 1: Classify Target Type

Determine what kind of provenance to trace:

02
Step 2a: Design Decision Tracing (Concepts)

Launch 4 parallel search agents (CASS, Handoff, Git, Research) and wait for all to complete. Backend: Agents use `Task(subagent_type="Explore")` which maps to `task(subagent_type="explore")` in OpenCode. See `skills/shared/SKILL.md` ("Runtime-Native Spawn Backend Selection") for the shared contract. Read `references/discovery-patterns.md` for agent definitions and prompts.

03
Step 2b: Git-Based Tracing (Commits/Refs)

Read `references/discovery-patterns.md` for git-based tracing commands.

04
Step 3: Build Timeline

Merge results from all sources into a single chronological timeline (oldest first). Deduplicate same-day/same-session events. Every claim needs a source citation.

05
Step 4: Extract Key Decisions

For each event in timeline, identify: What changed: The decision or evolution Why: Reasoning if available Who: Session/author/commit author Evidence: Link to source (session path, file, commit)

06
Step 5: Write Trace Report

Write to: `.agents/research/YYYY-MM-DD-trace-<concept-slug>.md` Read `references/report-template.md` for the full report format and deduplication rules.

07
Step 6: Report to User

Tell the user: Concept traced successfully Timeline of evolution (key dates) Most significant decisions Location of trace report

Discussion

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