skills.rest
KKenny0
KKenny0COMMUNITY
Explore all skills by this author →
Website𝕏@KennyYeah01GitHub

query

Query the decision replay index for project history evidence.

2|Updated Apr 11, 2026
Search Tags:#recall#decision#memory#evidence#query#traceability#project-history
One-click install
npx skills add https://github.com/KKenny0/Lode --skill query-kkenny0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: query
Source: https://github.com/KKenny0/Lode/tree/main/skills/query
Command: npx skills add https://github.com/KKenny0/Lode --skill query-kkenny0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) components.

What problem does it solve?

Querying the decision replay index to surface why a project path was chosen, what alternatives were rejected, and what open questions remain.

Core Features & Use Cases

  • Narrow decision evidence by project context and mode (why / alternatives / revisit / impact / free) to surface relevant decisions.
  • Retrieve and present source refs, timestamps, and artifact hints to inform architecture, prompts, contracts, and roadmaps.
  • Use case: during a design review, quickly surface why a previous approach was favored and what evidence supported it.

Quick Start

Ask a targeted question to surface cited decision evidence from Lode's memory.

Frequently Asked Questions about query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve past project decisions with cited evidence?▼

To retrieve past project decisions with cited evidence, query the decision replay index. This narrows evidence to relevant decision nodes and returns source_entry_refs, timestamps, and open_questions without modifying memory.

What is the best way to surface why a specific architecture path was chosen?▼

The best way to surface why an architecture path was chosen is to query decision history using the why mode. This filters the replay index to return the exact source_entry_refs and artifact hints supporting the selected path.

Can I find what alternatives were rejected during a design review?▼

Yes, you can find rejected alternatives during a design review by querying decision history with the alternatives mode. This surfaces the specific evidence and source refs explaining why previous approaches were rejected.

Does querying project history modify existing memory entries?▼

No, querying project history does not modify memory entries or write new records. The query process strictly reads the decision replay index to surface historical evidence and open_questions without mutating the underlying memory.

How do I narrow decision evidence by project context?▼

You narrow decision evidence by project context by asking a targeted question against the replay index using modes like why, alternatives, revisit, impact, or free. This filters the retrieved evidence to match the specific project context.

Related Skills

Explore More Software Engineering Skills→
KKenny0KKenny0
2

roadmap

Build a Markdown decision roadmap from weekly raw entries.

Community
Advanced
giovannimnzgiovannimnz

gsd-research-phase

Perform targeted domain research and generate a .planning/research/<name>.md findings document.

Community
Intermediate
OutlineDrivenOutlineDriven
5

memory-update

Scan session transcripts to extract save-worthy moments and write memory files.

Official
Advanced
kudrmaxkudrmax
1

search-conversations

Search past Claude Code sessions across projects using keyword queries.

Community
Intermediate