.claude/skills/aget-record-observation/SKILL.md
Record research observations into AGET KB without committing specs. Use when discovering vocabulary candidates, RQ proposals, web findings, patterns, or observations mid-session that should be preserved before continuing.
npx skillsauth add aget-framework/template-advisor-aget aget-record-observationInstall 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.
You are recording research observations for the AGET knowledge base.
Renamed: /aget-record-observation → /aget-record-observation per S-V-O naming convention (L584) and ACM SIGSOFT "Observation" grounding.
$ARGUMENTS
Detect the input mode based on $ARGUMENTS:
| Input Pattern | Mode | Behavior |
|---------------|------|----------|
| Empty or blank | Autonomous | Scan session, identify and capture valuable signals (~2 min) |
| Time pattern: 5min, 10 min, 20min, 30 min | Time-Budget | Scan session with depth scaled to time budget |
| Text with signal keywords | Explicit | Capture the specific signal provided |
| Other text | Explicit | Capture as general observation |
When invoked as /aget-record-observation with no arguments:
When invoked as /aget-record-observation <duration> (e.g., /aget-record-observation 10min):
| Time Budget | Depth | Actions | |-------------|-------|---------| | 2-5 min | Shallow | Scan + capture raw signals to session file | | 10 min | Medium | Classify + link signals to existing vocabulary terms | | 20 min | Deep | Interlink + propose RQs + draft L-doc candidates | | 30+ min | Full | Formalize with traceability, update session summary |
When invoked as /aget-record-observation "<signal>":
Classify the input and route to appropriate target:
| Signal Type | Indicator Keywords | Target Location | |-------------|-------------------|-----------------| | Vocabulary candidate | "term:", "concept:", "definition:", "vocabulary" | Session file - Vocabulary Candidates section | | Research question | "RQ:", "question:", "how does", "why does", "what is" | Session file - Research Questions section | | Web research finding | "source:", "URL:", "according to", "web search" | Session file - Web Findings section | | L-doc draft | "finding:", "lesson:", "L-doc", "learned:" | Session file - Findings section | | Pattern observation | "pattern:", "anti-pattern:", "noticed:", "observed:" | Session file - Patterns section | | Process gap | "gap:", "missing:", "SOP:", "template:" | Session file - Process Gaps section | | General observation | (default) | Session file - Observations section |
Append to current session file (if exists in sessions/session_YYYY-MM-DD_*.md):
### [Signal Type] - [ISO Timestamp]
**Source**: [User input / Session scan / Analysis]
**Content**:
[Captured signal]
**Status**: Captured (pending review at wind_down)
If no session file exists, create capture note in scratchpad with timestamp.
These are INVIOLABLE - you MUST NOT violate these constraints:
specs/CLI_VOCABULARY.md - vocabulary requires deliberate enhancement session per SOP_ONTOLOGY_ENHANCEMENT.mdspecs/CLI_SUBSYSTEM_SPEC.md - specs require deliberate enhancement sessionplanning/RESEARCH_BACKLOG.md directly - use session capture, formalize at wind_downsessions/Per AGET theoretical grounding:
This skill implements the "capture early, commit deliberately" pattern with adaptive depth.
| Link | Reference | |------|-----------| | Vocabulary | Capture_Protocol (CLI_VOCABULARY.md v1.30.0) | | Requirements | R-CLI-082, R-CLI-083 (CLI_SUBSYSTEM_SPEC.md v1.10.0) | | Skill Spec | SKILL-004 | | L-docs | L570, L571, L574 | | RQ | RQ-058, RQ-059, RQ-060 | | Pattern | Autonomous-Explicit Continuum (POC-013) |
testing
End AGET session with state capture and sanity checks
tools
Initialize AGET session with status briefing
development
Research a topic across the knowledge base before implementation. Searches L-docs, patterns, PROJECT_PLANs, SOPs, and governance for relevant context.
development
Save workflow state for resume/recovery. Use at natural breakpoints before context-intensive operations, major refactors, or session interruptions.