Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

[P0] Create research prompt template library (skills/research/) #974

New Issue
Closed
opened 2026-03-22 19:08:52 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-22 19:08:52 +00:00
Collaborator
Copy Link

Parent

  • #972 — [GOVERNING] Replacing Claude — Autonomous Research Pipeline Spec

Objective

Crystallize the structured query patterns that make Claude's research effective into reusable markdown templates with slot-fill placeholders. This is prompt engineering as a durable artifact.

Scope

Create 6 template files under skills/research/:

  1. tool_evaluation.md — "Find all shipping tools for {domain}"
  2. architecture_spike.md — "How to connect {system_a} to {system_b}"
  3. game_analysis.md — "Evaluate {game} for AI agent play"
  4. integration_guide.md — "Wire {tool} into {stack} with code"
  5. state_of_art.md — "What exists in {field} as of {date}"
  6. competitive_scan.md — "How does {project} compare to {alternatives}"

Each template has:

  • YAML frontmatter: name, type, typical query count, expected output length, cascade_tier hint
  • Body with {slot} placeholders
  • Clear output format constraints (tables, headers, structured markdown)

Key Design Notes

  • Templates are what transform a vague question into a structured research query
  • The cascade_tier hint tells the orchestrator which LLM tier to use (groq_preferred, local_ok, etc.)
  • Timmy fills slots from Gitea issue description or chat message
  • These should be reviewed by rockachopa before finalizing

Effort Estimate

4 hours

Acceptance Criteria

  • 6 template files exist under skills/research/
  • Each has valid YAML frontmatter with cascade_tier
  • Each has {slot} placeholders in the body
  • Templates produce well-structured prompts when filled
## Parent - #972 — [GOVERNING] Replacing Claude — Autonomous Research Pipeline Spec ## Objective Crystallize the structured query patterns that make Claude's research effective into reusable markdown templates with slot-fill placeholders. This is prompt engineering as a durable artifact. ## Scope Create 6 template files under `skills/research/`: 1. **`tool_evaluation.md`** — "Find all shipping tools for `{domain}`" 2. **`architecture_spike.md`** — "How to connect `{system_a}` to `{system_b}`" 3. **`game_analysis.md`** — "Evaluate `{game}` for AI agent play" 4. **`integration_guide.md`** — "Wire `{tool}` into `{stack}` with code" 5. **`state_of_art.md`** — "What exists in `{field}` as of `{date}`" 6. **`competitive_scan.md`** — "How does `{project}` compare to `{alternatives}`" Each template has: - YAML frontmatter: name, type, typical query count, expected output length, `cascade_tier` hint - Body with `{slot}` placeholders - Clear output format constraints (tables, headers, structured markdown) ## Key Design Notes - Templates are what transform a vague question into a structured research query - The `cascade_tier` hint tells the orchestrator which LLM tier to use (groq_preferred, local_ok, etc.) - Timmy fills slots from Gitea issue description or chat message - These should be reviewed by rockachopa before finalizing ## Effort Estimate 4 hours ## Acceptance Criteria - [ ] 6 template files exist under `skills/research/` - [ ] Each has valid YAML frontmatter with cascade_tier - [ ] Each has `{slot}` placeholders in the body - [ ] Templates produce well-structured prompts when filled
claude was assigned by Rockachopa 2026-03-22 21:44:42 +00:00
Rockachopa commented 2026-03-22 22:43:47 +00:00
Owner
Copy Link

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/999

Added 6 research prompt templates under skills/research/ with YAML frontmatter (including cascade_tier), slot placeholders, structured output formats, and research step guidance. All acceptance criteria met.

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/999 Added 6 research prompt templates under `skills/research/` with YAML frontmatter (including cascade_tier), slot placeholders, structured output formats, and research step guidance. All acceptance criteria met.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#974
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?