Sloppify
This commit is contained in:
25
ideas/ai-knowledge/codebase-qa-agent.md
Normal file
25
ideas/ai-knowledge/codebase-qa-agent.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Codebase Q&A Agent
|
||||
|
||||
Provide accurate, source-grounded answers about your repositories using retrieval-augmented generation over code, docs, and architecture notes.
|
||||
|
||||
## Problem
|
||||
Developers lose time searching across files and tribal knowledge to answer implementation questions that should be discoverable.
|
||||
|
||||
## Core capabilities
|
||||
- Index source code, READMEs, ADRs, and API specs.
|
||||
- Retrieve relevant snippets with file and line citations.
|
||||
- Answer natural-language questions like ownership, flow, and integration points.
|
||||
- Maintain freshness through incremental indexing on push.
|
||||
|
||||
## MVP scope
|
||||
- Start with one repository and language-aware chunking.
|
||||
- Chat interface with citation-first responses.
|
||||
- Permission-aware retrieval for private code.
|
||||
|
||||
## Success criteria
|
||||
- Faster onboarding and reduced interrupt load on senior engineers.
|
||||
- Higher answer trust due to verifiable citations.
|
||||
|
||||
## Stretch ideas
|
||||
- Generate architecture maps from indexed call graphs.
|
||||
- Detect stale docs by comparing docs against current code behavior.
|
||||
25
ideas/ai-knowledge/meeting-notes-pipeline.md
Normal file
25
ideas/ai-knowledge/meeting-notes-pipeline.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Meeting Notes -> Action Items Pipeline
|
||||
|
||||
Convert meeting transcripts into structured tasks, owners, and deadlines, then sync them automatically to your issue tracker.
|
||||
|
||||
## Problem
|
||||
Important decisions and follow-ups get buried in long meeting transcripts, causing missed commitments and duplicate work.
|
||||
|
||||
## Core capabilities
|
||||
- Ingest transcripts from calls, recordings, or notes.
|
||||
- Extract action items with owner, priority, and due date confidence.
|
||||
- Generate issue drafts for GitHub, Gitea, Jira, or Linear.
|
||||
- Keep traceability by linking tasks back to transcript evidence.
|
||||
|
||||
## MVP scope
|
||||
- Support plain text and common transcript formats.
|
||||
- Human review queue before task creation.
|
||||
- Daily digest of open actions by team or project.
|
||||
|
||||
## Success criteria
|
||||
- Higher completion rate of meeting-derived tasks.
|
||||
- Reduced time spent manually rewriting notes into tickets.
|
||||
|
||||
## Stretch ideas
|
||||
- Identify unresolved decisions across recurring meetings.
|
||||
- Build a knowledge graph of owners, systems, and commitments.
|
||||
Reference in New Issue
Block a user