/research-triage - Research Outcome Triage

Triage research manifests to terminal outcomes per ADR-208 Research-to-Product Promotion Lifecycle.

Usage

# List un-triaged research (93 manifests at MONITOR status)
/research-triage --list

# Show triage statistics
/research-triage --stats

# Validate all manifests against schema
/research-triage --validate

# Triage a specific manifest interactively
/research-triage 2026-01-15-example-research.yaml

# Triage with explicit outcome
/research-triage 2026-01-15-example.yaml --outcome product \
  --repository submodules/products/my-product \
  --rationale "Research validated and became standalone product"

# Archive research that has no viable path
/research-triage 2026-01-15-old-research.yaml --outcome archive \
  --rationale "Technology superseded by newer approach"

# Dry run (show what would change without writing)
/research-triage 2026-01-15-example.yaml --outcome component --dry-run

System Prompt

EXECUTION DIRECTIVE: When the user invokes /research-triage, you MUST:

1. IMMEDIATELY execute the appropriate action based on arguments
2. Parse the user's arguments to determine mode: --list, --stats, --validate, or triage
3. Run python3 scripts/research_triage.py with the appropriate flags
4. Display results clearly

Execution Modes

Mode 1: List un-triaged manifests

cd submodules/core/coditect-core
python3 scripts/research_triage.py --list

Mode 2: Statistics

cd submodules/core/coditect-core
python3 scripts/research_triage.py --stats

Mode 3: Validate

cd submodules/core/coditect-core
python3 scripts/research_triage.py --validate

Mode 4: Interactive triage (manifest name given, no --outcome)

When a manifest name is provided without --outcome, enter interactive mode:

1. Read the manifest YAML
2. Show the user: topic, category, recommendation, confidence, artifacts
3. Ask the user to choose an outcome using AskUserQuestion:

Which outcome for this research?

- Product: Research becomes a standalone product (new repo, new TRACK)
- Prototype: Experimental validation before product commitment (labs/)
- Component: Absorbed into coditect-core as skill/agent/command
- Archive: No viable path forward, document lessons learned

4. Based on selection, ask follow-up questions:

   • Product: Repository path, project ID, launch target
   • Prototype: Repository path, graduation criteria, graduation target
   • Component: Type (skill/agent/command), name, description
   • Archive: Reason, lessons learned

5. Execute: python3 scripts/research_triage.py --manifest <name> --outcome <choice> --rationale "<rationale>" [options]

6. Show results including:

   • Manifest updated
   • Registry updated
   • projects.db registration (product only)
   • Track entry suggestions (product/component)

Mode 5: Non-interactive triage (manifest + --outcome given)

cd submodules/core/coditect-core
python3 scripts/research_triage.py --manifest <name> --outcome <outcome> \
  --rationale "<rationale>" [--repository <path>] [--component-name <name>]

Post-Triage Actions

After successful triage:

1. Confirm the manifest was updated
2. Show registry count changes
3. Display TRACK entry suggestions for product/component outcomes
4. Remind user to commit: git add internal/research/manifests/ && git commit

Outcomes (ADR-208)

Outcome	Description	Example
product	Research becomes standalone product	codestoryai-sidecar → coditect-development-studio
prototype	Experimental validation in labs/	continual-learning → coditect-nested-learning
component	Absorbed into coditect-core	scaling-agent-systems → scaling-agent-orchestration skill
archive	No viable path, document lessons	Superseded technology evaluations

What Gets Updated

Action	Applies To	Automatic
Manifest YAML outcome fields	All outcomes	Yes
Recommendation/confidence upgrade	product, component, prototype	Yes
Registry README.md counts	All outcomes	Yes
projects.db registration	product only	Yes
TRACK entry suggestions	product, component	Suggested (manual)

Related

• ADR: ADR-208 Research-to-Product Promotion Lifecycle
• ADR: ADR-207 Research Artifact Organization Taxonomy
• Schema: config/schemas/research-manifest-v1.schema.json (v1.1.0)
• Registry: internal/research/manifests/README.md
• Script: scripts/research_triage.py

Success Output

Triage Result for 2026-01-15-example.yaml:
  Outcome: product
  - Updated manifest with outcome=product
  - Wrote 2026-01-15-example.yaml
  - Updated registry row for 2026-01-15-example.yaml
  - Updated registry totals: 97 manifests, 5 triaged, 92 monitor
  - Wrote updated README.md
  - Registered project 'example' in projects.db

  Track Suggestions:
    Suggested TRACK entries for product 'example':
      Track N (GTM): Add launch task for submodules/products/example
      Example: N.X.1: Set up example project structure

Completion Checklist

• Manifest YAML updated with outcome fields
• Registry README.md counts updated
• projects.db registered (if product)
• TRACK entry suggestions shown (if product/component)
• User reminded to commit changes

Failure Indicators

• Manifest file not found
• Invalid outcome specified
• Registry README.md parse error
• projects.db write failure

---

Command Version: 1.0.0 Created: 2026-02-16 Author: CODITECT Core Team ADR: ADR-208