spec-kitty-cli 0.5.0__tar.gz → 0.7.0__tar.gz

{spec_kitty_cli-0.5.0/.kittify/active-mission/commands → spec_kitty_cli-0.7.0/.kittify/missions/research/command-templates}/implement.md

@@ -17,29 +17,65 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 ## Location Pre-flight Check (CRITICAL for AI Agents)
 
-Before proceeding with implementation, verify you are in the correct working directory:
+Before proceeding with implementation, verify you are in the correct working directory by running the shared pre-flight validation:
 
-**Check your current branch:**
-```bash
-git branch --show-current
-```
-
-**Expected output:** A feature branch like `001-feature-name`
-**If you see `main`:** You are in the wrong location!
+```python
+from specify_cli.guards import validate_worktree_location
 
-**This command MUST run from a feature worktree, not the main repository.**
+# Validate location
+result = validate_worktree_location()
+if not result.is_valid:
+    print(result.format_error())
+    print("\nThis command MUST run from a feature worktree, not the main repository.")
+    exit(1)
+```
 
-If you're on the `main` branch:
-1. Check for available worktrees: `ls .worktrees/`
-2. Navigate to the appropriate feature worktree: `cd .worktrees/<feature-name>`
-3. Verify you're in the right place: `git branch --show-current` should show the feature branch
-4. Then re-run this command
+**What this validates**:
+- Current branch follows the feature pattern like `001-feature-name`
+- You're not attempting to run from `main` or any release branch
+- The validator prints clear navigation instructions if you're outside the feature worktree
 
-The script will fail if you're not in a feature worktree.
 **Path reference rule:** When you mention directories or files, provide either the absolute path or a path relative to the project root (for example, `kitty-specs/<feature>/tasks/`). Never refer to a folder by name alone.
 
 This is intentional - worktrees provide isolation for parallel feature development.
 
+## Citation Tracking Requirements (Research Mission)
+
+As you conduct research and gather evidence, you MUST maintain proper citation tracking:
+
+### Evidence Log Maintenance
+
+**File**: `research/evidence-log.csv`
+
+**For each source you review**:
+1. Read the source and extract key findings
+2. Add a row to evidence-log.csv with:
+   - timestamp: Current time in ISO format (YYYY-MM-DDTHH:MM:SS)
+   - source_type: journal | conference | book | web | preprint
+   - citation: Full citation in BibTeX or APA format
+   - key_finding: 1-2 sentence summary of main takeaway
+   - confidence: high | medium | low (based on source quality)
+   - notes: Additional context, caveats, or limitations
+
+**Citation Format Examples**:
+- BibTeX: `@article{smith2024,author={Smith et al.},title={Paper Title},journal={Journal},year={2024}}`
+- APA: `Smith, J., & Lee, K. (2024). Paper title. Journal Name, 10(2), 123-145.`
+- Simple: `Smith (2024). Paper title. Journal Name. https://doi.org/...`
+
+### Source Registry Maintenance
+
+**File**: `research/source-register.csv`
+
+**When you discover a new source**:
+1. Add to source-register.csv immediately
+2. Assign unique source_id (e.g., "smith2024")
+3. Include full citation and URL
+4. Mark status as "pending"
+5. Update status to "reviewed" after reading
+6. Assign relevance rating (high/medium/low)
+
+**Validation**: Citations will be validated during `/spec-kitty.review`. Errors block review, warnings are advisory.
+
 ## ⚠️ CRITICAL: Review Feedback Check
 
 **Before you start implementing**, check for prior review feedback:
@@ -178,7 +214,7 @@ This is intentional - worktrees provide isolation for parallel feature developme
    - **Kanban discipline**: Use the lane helper scripts to keep the prompt in `tasks/doing/`, update the Activity Log, and capture your shell PID (`echo $$`). These should already be complete from step 3—verify before coding.
 
 7. Implementation execution rules:
-   - **Setup first**: Initialize project structure, dependencies, configuration
+   - **Setup first**: Initialize feature scaffolding, dependencies, configuration
    - **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios
    - **Core development**: Implement models, services, CLI commands, endpoints
    - **Integration work**: Database connections, middleware, logging, external services
@@ -270,4 +306,3 @@ Leverage your agent’s native orchestration so one work package advances while
 - **Amazon Q Developer CLI** – Use Container Use recipes to create multiple isolated Q sessions so one agent handles reviews while another implements new changes.[^amazonq_parallel]
 
 If an agent lacks built-in subagents, mimic the pattern manually: open a second terminal, move a review prompt to `tasks/doing/`, and run the reviewer commands there while your primary session keeps coding.
-

{spec_kitty_cli-0.5.0/.kittify/templates/commands → spec_kitty_cli-0.7.0/.kittify/missions/research/command-templates}/merge.md

@@ -4,10 +4,6 @@ scripts:
   sh: ".kittify/scripts/bash/merge-feature.sh"
   ps: ".kittify/scripts/powershell/Merge-Feature.ps1"
 ---
-**Path reference rule:** When you mention directories or files, provide either the absolute path or a path relative to the project root (for example, `kitty-specs/<feature>/tasks/`). Never refer to a folder by name alone.
-
-*Path: [templates/commands/merge.md](templates/commands/merge.md)*
-
 
 # Merge Feature Branch
 
@@ -20,13 +16,65 @@ Before running this command:
 1. ✅ Feature must pass `/spec-kitty.accept` checks
 2. ✅ All work packages must be in `tasks/done/`
 3. ✅ Working directory must be clean (no uncommitted changes)
-4. ✅ Run the command from the feature worktree (Spec Kitty will move the merge to the primary repo automatically)
+4. ✅ You must be on the feature branch (or in its worktree)
+
+## Location Pre-flight Check (CRITICAL for AI Agents)
+
+Before merging, verify you are in the correct working directory by running the shared pre-flight validation:
+
+```python
+from specify_cli.guards import validate_worktree_location
+
+# Validate location
+result = validate_worktree_location()
+if not result.is_valid:
+    print(result.format_error())
+    print("\nThis command MUST run from a feature worktree, not the main repository.")
+    exit(1)
+```
+
+**What this validates**:
+- Current branch follows the feature pattern like `001-feature-name`
+- You're not attempting to run from `main` or any release branch
+- The validator prints clear navigation instructions if you're outside the feature worktree
+
+**Path reference rule:** When you mention directories or files, provide either the absolute path or a path relative to the project root (for example, `kitty-specs/<feature>/tasks/`). Never refer to a folder by name alone.
+
+## Final Research Integrity Check
+
+Before merging research to main, perform final validation:
+
+```bash
+# Quick citation validation
+python -c "
+from pathlib import Path
+from specify_cli.validators.research import validate_citations, validate_source_register
+
+feature_dir = Path('kitty-specs/$FEATURE_SLUG')
+evidence = feature_dir / 'research' / 'evidence-log.csv'
+sources = feature_dir / 'research' / 'source-register.csv'
+
+if evidence.exists():
+    result = validate_citations(evidence)
+    if result.has_errors:
+        print('ERROR: Evidence log has citation errors')
+        exit(1)
+
+if sources.exists():
+    result = validate_source_register(sources)
+    if result.has_errors:
+        print('ERROR: Source register has errors')
+        exit(1)
+
+print('✓ Citations validated')
+"
+```
 
 ## What This Command Does
 
 1. **Detects** your current feature branch and worktree status
 2. **Verifies** working directory is clean
-3. **Switches** to the target branch (default: `main`) in the primary repository
+3. **Switches** to the target branch (default: `main`)
 4. **Updates** the target branch (`git pull --ff-only`)
 5. **Merges** the feature using your chosen strategy
 6. **Optionally pushes** to origin
@@ -142,7 +190,7 @@ my-project/                    # Main repo (main branch)
 1. **Main branch** stays in the primary repo root
 2. **Feature branches** live in `.worktrees/<feature-slug>/`
 3. **Work on features** happens in their worktrees (isolation)
-4. **Merge from worktrees** using this command – the CLI will hop to the primary repo for the Git merge
+4. **Merge from worktrees** using this command
 5. **Cleanup is automatic** - worktrees removed after merge
 
 ### Why Worktrees?
@@ -207,11 +255,10 @@ git branch -d <feature-branch>
 ## Safety Features
 
 1. **Clean working directory check** - Won't merge with uncommitted changes
-2. **Primary repo hand-off** - Automatically runs Git operations from the main checkout when invoked in a worktree
-3. **Fast-forward only pull** - Won't proceed if main has diverged
-4. **Graceful failure** - If merge fails, you can fix manually
-5. **Optional operations** - Push, branch delete, and worktree removal are configurable
-6. **Dry run mode** - Preview exactly what will happen
+2. **Fast-forward only pull** - Won't proceed if main has diverged
+3. **Graceful failure** - If merge fails, you can fix manually
+4. **Optional operations** - Push, branch delete, and worktree removal are configurable
+5. **Dry run mode** - Preview exactly what will happen
 
 ## Examples
 

{spec_kitty_cli-0.5.0/.kittify/active-mission/commands → spec_kitty_cli-0.7.0/.kittify/missions/research/command-templates}/plan.md

@@ -18,25 +18,25 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 ## Location Pre-flight Check (CRITICAL for AI Agents)
 
-Before proceeding with planning, verify you are in the correct working directory:
+Before proceeding with planning, verify you are in the correct working directory by running the shared pre-flight validation:
 
-**Check your current branch:**
-```bash
-git branch --show-current
-```
-
-**Expected output:** A feature branch like `001-feature-name`
-**If you see `main`:** You are in the wrong location!
+```python
+from specify_cli.guards import validate_worktree_location
 
-**This command MUST run from a feature worktree, not the main repository.**
+# Validate location
+result = validate_worktree_location()
+if not result.is_valid:
+    print(result.format_error())
+    print("\nThis command MUST run from a feature worktree, not the main repository.")
+    exit(1)
+```
 
-If you're on the `main` branch:
-1. Check for available worktrees: `ls .worktrees/`
-2. Navigate to the appropriate feature worktree: `cd .worktrees/<feature-name>`
-3. Verify you're in the right place: `git branch --show-current` should show the feature branch
-4. Then re-run this command
+**What this validates**:
+- Current branch follows the feature pattern like `001-feature-name`
+- You're not attempting to run from `main` or any release branch
+- The validator prints clear navigation instructions if you're outside the feature worktree
 
-The script will fail if you're not in a feature worktree. This is intentional - worktrees provide isolation for parallel feature development.
+**Path reference rule:** When you mention directories or files, provide either the absolute path or a path relative to the project root (for example, `kitty-specs/<feature>/tasks/`). Never refer to a folder by name alone.
 
 ## Planning Interrogation (mandatory)
 

spec_kitty_cli-0.7.0/.kittify/missions/research/command-templates/review.md

@@ -0,0 +1,155 @@
+---
+description: Perform structured research review with citation validation.
+scripts:
+  sh: scripts/bash/check-prerequisites.sh --json --include-tasks
+  ps: scripts/powershell/check-prerequisites.ps1 -Json -IncludeTasks
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Location Pre-flight Check (CRITICAL for AI Agents)
+
+Before proceeding with review, verify you are in the correct working directory by running the shared pre-flight validation:
+
+```python
+from specify_cli.guards import validate_worktree_location
+
+# Validate location
+result = validate_worktree_location()
+if not result.is_valid:
+    print(result.format_error())
+    print("\nThis command MUST run from a feature worktree, not the main repository.")
+    exit(1)
+```
+
+**What this validates**:
+- Current branch follows the feature pattern like `001-feature-name`
+- You're not attempting to run from `main` or any release branch
+- The validator prints clear navigation instructions if you're outside the feature worktree
+
+**Path reference rule:** When you mention directories or files, provide either the absolute path or a path relative to the project root (for example, `kitty-specs/<feature>/tasks/`). Never refer to a folder by name alone.
+
+## Citation Validation (Research Mission Specific)
+
+Before reviewing research tasks, validate all citations and sources:
+
+```python
+from pathlib import Path
+from specify_cli.validators.research import validate_citations, validate_source_register
+
+# Validate evidence log
+evidence_log = FEATURE_DIR / "research" / "evidence-log.csv"
+if evidence_log.exists():
+    result = validate_citations(evidence_log)
+    if result.has_errors:
+        print(result.format_report())
+        print("\nERROR: Citation validation failed. Fix errors before proceeding.")
+        exit(1)
+    elif result.warning_count > 0:
+        print(result.format_report())
+        print("\nWarnings found - consider addressing for better citation quality.")
+
+# Validate source register
+source_register = FEATURE_DIR / "research" / "source-register.csv"
+if source_register.exists():
+    result = validate_source_register(source_register)
+    if result.has_errors:
+        print(result.format_report())
+        print("\nERROR: Source register validation failed.")
+        exit(1)
+```
+
+**Validation Requirements**:
+- All sources must be documented with unique `source_id` entries.
+- Citations must be present in both CSVs (format warnings are advisory).
+- Confidence levels should be filled for evidence entries.
+- Research review cannot proceed if validation reports blocking errors.
+
+## Outline
+
+1. Run `{SCRIPT}` from repo root; capture `FEATURE_DIR`, `AVAILABLE_DOCS`, and `tasks.md` path.
+
+2. Determine the review target:
+   - If user input specifies a filename, validate it exists under `tasks/for_review/` (support phase subdirectories).
+   - Otherwise, select the oldest file in `tasks/for_review/` (lexical order is sufficient because filenames retain task ordering).
+   - Abort with instructional message if no files are waiting for review.
+
+3. Load context for the selected task:
+   - Read the prompt file frontmatter (lane MUST be `for_review`); note `task_id`, `phase`, `agent`, `shell_pid`.
+   - Read the body sections (Objective, Context, Implementation Guidance, etc.).
+   - Consult supporting documents as referenced: constitution, plan, spec, data-model, research, quickstart, code changes.
+   - Review the associated code in the repository (diffs, tests, docs) to validate the implementation.
+
+4. Conduct the review:
+   - Verify implementation against the prompt’s Definition of Done and Review Guidance.
+   - Run required tests or commands; capture results.
+   - Document findings explicitly: bugs, regressions, missing tests, risks, or validation notes.
+
+5. Decide outcome:
+  - **Needs changes**:
+     * Append a new entry in the prompt’s **Activity Log** detailing feedback (include timestamp, reviewer agent, shell PID).
+     * Update frontmatter `lane` back to `planned`, clear `assignee` if necessary, keep history entry.
+     * Add/revise a `## Review Feedback` section (create if missing) summarizing action items.
+     * Run `.kittify/scripts/bash/tasks-move-to-lane.sh <FEATURE> <TASK_ID> planned --note "Returned for changes"` (use the PowerShell equivalent on Windows) so the move and history update are staged consistently.
+  - **Approved**:
+     * Append Activity Log entry capturing approval details (capture shell PID via `echo $$` or helper script).
+     * Update frontmatter: set `lane=done`, set reviewer metadata (`agent`, `shell_pid`), optional `assignee` for approver.
+     * Use helper script to mark the task complete in `tasks.md` (see Step 6).
+     * Run `.kittify/scripts/bash/tasks-move-to-lane.sh <FEATURE> <TASK_ID> done --note "Approved for release"` (PowerShell variant available) to transition the prompt into `tasks/done/`.
+
+6. Update `tasks.md` automatically:
+   - Run `scripts/bash/mark-task-status.sh --task-id <TASK_ID> --status done` (POSIX) or `scripts/powershell/Set-TaskStatus.ps1 -TaskId <TASK_ID> -Status done` (PowerShell) from repo root.
+   - Confirm the task entry now shows `[X]` and includes a reference to the prompt file in its notes.
+
+7. Produce a review report summarizing:
+   - Task ID and filename reviewed.
+  - Approval status and key findings.
+   - Tests executed and their results.
+   - Follow-up actions (if any) for other team members.
+   - Reminder to push changes or notify teammates as per project conventions.
+
+Context for review: {ARGS}
+
+All review feedback must live inside the prompt file, ensuring future implementers understand historical decisions before revisiting the task.
+
+## Citation Validation (Research Mission Specific)
+
+Before reviewing research tasks, validate all citations and sources:
+
+```python
+from pathlib import Path
+from specify_cli.validators.research import validate_citations, validate_source_register
+
+# Validate evidence log
+evidence_log = FEATURE_DIR / "research" / "evidence-log.csv"
+if evidence_log.exists():
+    result = validate_citations(evidence_log)
+    if result.has_errors:
+        print(result.format_report())
+        print("\nERROR: Citation validation failed. Fix errors before proceeding.")
+        exit(1)
+    elif result.warning_count > 0:
+        print(result.format_report())
+        print("\nWarnings found - consider addressing for better citation quality.")
+
+# Validate source register
+source_register = FEATURE_DIR / "research" / "source-register.csv"
+if source_register.exists():
+    result = validate_source_register(source_register)
+    if result.has_errors:
+        print(result.format_report())
+        print("\nERROR: Source register validation failed.")
+        exit(1)
+```
+
+**Validation Requirements**:
+- All sources must be documented with unique `source_id` entries.
+- Citations must be present in both CSVs (format warnings are advisory).
+- Confidence levels should be filled for evidence entries.
+- Research review cannot proceed if validation reports blocking errors.

{spec_kitty_cli-0.5.0 → spec_kitty_cli-0.7.0}/.kittify/missions/research/mission.yaml

@@ -23,16 +23,16 @@ workflow:
 artifacts:
   required:
     - spec.md              # Research question and scope
-    - plan.md             # Methodology plan
-    - tasks.md            # Research tasks
-    - findings.md         # Research findings
+    - plan.md              # Methodology plan
+    - tasks.md             # Research work packages
+    - findings.md          # Synthesized findings
   optional:
-    - sources/            # Source documents
-    - data/              # Raw data
-    - analysis/          # Analysis outputs
-    - literature-review.md
-    - methodology.md
-    - synthesis.md
+    - sources/             # Source documents
+    - data/                # Raw data
+    - analysis/            # Analysis outputs
+    - literature-review.md # Optional extended literature review
+    - methodology.md       # Detailed methodology appendix
+    - synthesis.md         # Synthesis notes or drafts
 
 # Path conventions for this mission
 paths:
@@ -68,15 +68,22 @@ mcp_tools:
 # Agent personality/instructions
 agent_context: |
   You are a research agent conducting systematic literature reviews and empirical research.
-  Your principles emphasize rigorous methodology, source documentation, and evidence synthesis.
-  You work in structured phases: question → methodology → gather → analyze → synthesize → publish.
+  Your mission is to maintain research integrity and methodological rigor throughout every phase.
 
-  Key practices:
-  - Document all sources with proper citations
-  - Clearly articulate research methodology
-  - Distinguish evidence from interpretation
-  - Identify limitations and future research directions
-  - Synthesize findings to answer research questions
+  Key Practices:
+  - Document ALL sources in research/source-register.csv with proper citations, URLs, and access dates.
+  - Extract findings to research/evidence-log.csv with confidence levels (high/medium/low) and contextual notes.
+  - Clearly articulate methodology decisions for reproducibility and peer review.
+  - Distinguish raw evidence from interpretation; cite every claim.
+  - Identify limitations, threats to validity, and alternative explanations.
+  - Synthesize findings so that each conclusion traces back to documented evidence rows.
+
+  Citation Standards:
+  - Use BibTeX or APA format (include DOI or URL when available).
+  - Track access dates for all online sources.
+  - Assign confidence levels commensurate with source quality.
+
+  Workflow Phases: question → methodology → gather → analyze → synthesize → publish.
 
 # Task metadata fields
 task_metadata:

spec_kitty_cli-0.7.0/.kittify/missions/research/templates/plan-template.md

@@ -0,0 +1,161 @@
+# Research Plan: [RESEARCH QUESTION]
+
+**Branch**: `[###-research-name]` | **Date**: [DATE] | **Spec**: [link]
+
+## Summary
+[One paragraph: research question + methodology + expected outcomes]
+
+## Research Context
+
+**Research Question**: [Primary question]  
+**Research Type**: Literature Review | Empirical Study | Case Study  
+**Domain**: [Academic field or industry domain]  
+**Time Frame**: [When research will be conducted]  
+**Resources Available**: [Databases, tools, budget, time]
+
+**Key Background**:
+- [Context point 1]
+- [Context point 2]
+
+## Methodology
+
+### Research Design
+
+**Approach**: [Systematic Literature Review | Survey | Experiment | Mixed Methods]
+
+**Phases**:
+1. **Question Formation** (Week 1)
+   - Define precise research question
+   - Identify sub-questions
+   - Establish scope and boundaries
+2. **Methodology Design** (Week 1-2)
+   - Select data collection methods
+   - Define analysis framework
+   - Establish quality criteria
+3. **Data Gathering** (Week 2-4)
+   - Search academic databases
+   - Screen sources for relevance
+   - Extract key findings
+   - Populate `research/evidence-log.csv`
+4. **Analysis** (Week 4-5)
+   - Code and categorize findings
+   - Identify patterns and themes
+   - Assess evidence quality
+5. **Synthesis** (Week 5-6)
+   - Draw conclusions
+   - Address research question
+   - Identify limitations
+6. **Publication** (Week 6)
+   - Write findings report
+   - Prepare presentation
+   - Share results
+
+### Data Sources
+
+**Primary Sources**:
+- [Database 1: e.g., IEEE Xplore, PubMed, arXiv]
+- [Database 2]
+
+**Secondary Sources**:
+- [Gray literature, industry reports, etc.]
+
+**Search Strategy**:
+- **Keywords**: [List search terms]
+- **Inclusion Criteria**: [What qualifies for review]
+- **Exclusion Criteria**: [What will be filtered out]
+
+### Analysis Framework
+
+**Coding Scheme**: [How findings will be categorized]  
+**Synthesis Method**: [Thematic analysis | Meta-analysis | Narrative synthesis]  
+**Quality Assessment**: [How source quality will be evaluated]
+
+## Data Management
+
+### Evidence Tracking
+
+**File**: `research/evidence-log.csv`  
+**Purpose**: Track all evidence collected with citations and findings
+
+**Columns**:
+- `timestamp`: When evidence collected (ISO format)
+- `source_type`: journal | conference | book | web | preprint
+- `citation`: Full citation (BibTeX or APA format)
+- `key_finding`: Main takeaway from this source
+- `confidence`: high | medium | low
+- `notes`: Additional context or caveats
+
+**Agent Guidance**:
+1. Read source and extract key finding.
+2. Add row to evidence-log.csv.
+3. Assign confidence level based on source quality and clarity.
+4. Note limitations or alternative interpretations.
+
+### Source Registry
+
+**File**: `research/source-register.csv`  
+**Purpose**: Maintain master list of all sources for bibliography
+
+**Columns**:
+- `source_id`: Unique identifier (e.g., "smith2025")
+- `citation`: Full citation
+- `url`: Link to source (if available)
+- `accessed_date`: When source was accessed
+- `relevance`: high | medium | low
+- `status`: reviewed | pending | archived
+
+**Agent Guidance**:
+1. Add source to register when first discovered.
+2. Update status as research progresses.
+3. Maintain relevance ratings to prioritize review.
+
+## Project Structure
+
+### Documentation (this research project)
+```
+kitty-specs/[###-research]/
+├── spec.md              # Research question and scope
+├── plan.md              # This file - methodology
+├── tasks.md             # Research work packages
+├── findings.md          # Research findings
+├── research/
+│   ├── evidence-log.csv      # All evidence with citations
+│   ├── source-register.csv   # Master source list
+│   └── methodology.md        # Detailed methodology (optional)
+└── data/                # Raw data (if empirical)
+```
+
+### Deliverables
+```
+findings/
+├── report.md           # Main research report
+├── bibliography.md     # Formatted bibliography
+└── presentation/       # Slides or summary (optional)
+```
+
+## Quality Gates
+
+### Before Data Gathering
+- [ ] Research question is clear and focused
+- [ ] Methodology is documented and reproducible
+- [ ] Data sources identified and accessible
+- [ ] Analysis framework defined
+
+### During Data Gathering
+- [ ] All sources documented in source-register.csv
+- [ ] Evidence logged with proper citations
+- [ ] Confidence levels assigned
+- [ ] Quality threshold maintained
+
+### Before Synthesis
+- [ ] All sources reviewed
+- [ ] Findings coded and categorized
+- [ ] Patterns identified
+- [ ] Limitations documented
+
+### Before Publication
+- [ ] Research question answered
+- [ ] All claims cited
+- [ ] Methodology clear and reproducible
+- [ ] Findings synthesized
+- [ ] Bibliography complete

spec_kitty_cli-0.7.0/.kittify/missions/research/templates/research/evidence-log.csv

@@ -0,0 +1,18 @@
+# Evidence Log: Track all research findings with citations
+#
+# Column Definitions:
+# - timestamp: When evidence was collected (ISO format: YYYY-MM-DDTHH:MM:SS)
+# - source_type: journal | conference | book | web | preprint
+# - citation: Full citation (BibTeX, APA, or Simple format)
+# - key_finding: Main takeaway from this source (1-2 sentences)
+# - confidence: high | medium | low (based on source quality and clarity)
+# - notes: Additional context, caveats, or methodological notes
+#
+# Validation: Citations must be non-empty, source_type must be valid
+# Format: BibTeX (@article{...}) or APA (Author (Year). Title.) recommended
+timestamp,source_type,citation,key_finding,confidence,notes
+2025-01-15T10:00:00,journal,"Smith, J. (2024). AI Code Assistants. Nature Comp Sci, 10(2), 123-145.",AI assistants improve productivity 30%,high,Meta-analysis of 50 peer-reviewed studies
+2025-01-15T11:30:00,conference,"@inproceedings{jones2024copilot,author={Jones et al.},title={Copilot Study},booktitle={ICSE},year={2024}}",Copilot acceptance rate averages 65%,medium,GitHub internal usage study
+2025-01-15T14:00:00,web,"GitHub Copilot Stats. https://github.blog/copilot-stats-2024",35M developers actively use Copilot,medium,Self-reported marketing data
+2025-01-15T15:30:00,preprint,"Lee, K. (2024). AI Pair Programming. arXiv:2024.12345",Real-time suggestions reduce onboarding time,low,Preprint pending peer review
+2025-01-16T09:00:00,book,"Brown, A. (2023). The AI Developer. O'Reilly Media.",Context-aware tools reduce cognitive load,high,Chapter 7 includes empirical study

spec_kitty_cli-0.7.0/.kittify/missions/research/templates/research/source-register.csv

@@ -0,0 +1,18 @@
+# Source Register: Master list of all research sources
+#
+# Column Definitions:
+# - source_id: Unique identifier (lowercase, no spaces, e.g., "smith2024")
+# - citation: Full citation (BibTeX or APA format)
+# - url: Direct link to source (DOI, arXiv, or web URL)
+# - accessed_date: Date source was accessed (YYYY-MM-DD)
+# - relevance: high | medium | low (to primary research question)
+# - status: reviewed | pending | archived
+#
+# Usage: Add sources when discovered, update status as research progresses
+# Validation: source_id must be unique
+source_id,citation,url,accessed_date,relevance,status
+smith2024,"Smith, J. (2024). AI Code Assistants. Nature Comp Sci, 10(2), 123-145.",https://doi.org/10.1038/example,2025-01-15,high,reviewed
+jones2024,"@inproceedings{jones2024copilot,author={Jones et al.},title={Copilot Study},booktitle={ICSE 2024},year={2024}}",https://dl.acm.org/example,2025-01-15,high,reviewed
+github2024,"GitHub Copilot Statistics. GitHub Blog.",https://github.blog/copilot-stats-2024,2025-01-15,medium,reviewed
+lee2024,"Lee, K. (2024). AI Pair Programming. arXiv:2024.12345",https://arxiv.org/abs/2024.12345,2025-01-15,low,pending
+brown2023,"Brown, A. (2023). The AI Developer: Human-Machine Collaboration. O'Reilly Media.",https://oreilly.com/example,2025-01-16,high,archived