From operator
Triage Operator documents by assessing content and routing to appropriate workflow stages
How this skill is triggered — by the user, by Claude, or both
Slash command
/operator:operator-triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Methodical workflow for reviewing Operator documents and deciding their next
Methodical workflow for reviewing Operator documents and deciding their next steps in the development pipeline.
Activate when:
operator-setup skill)Use the cached session from .operator file, or re-authenticate if expired.
Either:
Read the document and determine:
| Aspect | Questions |
|---|---|
| Type | Bug report? Feature idea? Architecture thought? UX flow? |
| Maturity | Raw capture? Explored concept? Clear specification? |
| Clarity | Ready to act on? Needs investigation first? |
Reference the docs framework: See docs/README.md for the complete decision flowchart and document type definitions.
Operator → Docs Routing (from docs/README.md):
| Operator Content | Routes To |
|---|---|
| Feature ideas | → Investigation or Proposal |
| Bug reports | → Lesson Learned (if solved) or Investigation (if unclear) |
| Architecture thoughts | → Architecture documentation |
| UX flow thoughts | → Interaction Design documentation |
| Work context | → Referenced in Sessions |
Decision Framework (simplified):
Is it a clear, solved problem?
→ Lesson Learned (document the fix)
Is it uncertain or needs research?
→ Investigation (explore before committing)
Is it a clear feature idea with known approach?
→ Proposal (define what and why)
Is it an approved proposal?
→ Plan (define how to build it)
Is it ready to implement?
→ Development (create worktree, start work)
Not ready to act on?
→ Fragment (capture for later)
Quick Actions:
| Route | Next Action |
|---|---|
| Investigation | Move to on-deck, launch investigator agent |
| Proposal | Create proposal doc using proposal-writer agent |
| Plan | Create dev plan using dev-plan-generator agent |
| Development | Create worktree using dev-kickoff skill |
| Lesson Learned | Create doc in docs/lessons-learned/ |
| Fragment | Move to fragments folder, revisit later |
| Defer | Move to backlog, note reason |
Create a task capturing:
Triage: <document-name> → <routing-decision>Example:
Subject: Triage: missing-feature.md → Investigation
Description:
**Source:** Operator/bugs/missing-feature.md
**Summary:**
- Reports that X doesn't work when Y
- Unclear if bug or missing feature
- Needs codebase exploration
**Decision:** Investigation
**Next Steps:**
1. Move to on-deck folder
2. Launch investigator agent
3. Create proposal based on findings
TaskList to show all pending triage decisions| Folder | Purpose |
|---|---|
fragments | Raw ideas, quick captures, incomplete thoughts |
bugs | Bug reports, issues to investigate |
on-deck | Ready for next action (investigation, proposal, etc.) |
proposals | Feature proposals awaiting approval |
archive | Completed or declined items |
npx claudepluginhub ichabodcole/project-docs-scaffold-template --plugin operatorDesigns and runs a documentation system for a team or product: planning what to document, choosing tools, organizing existing docs, fixing stale docs, and establishing maintenance cadence.
Organizes project documentation into intent-based structure (BUILD/FIX/UNDERSTAND/LOOKUP) by auditing files and creating directories. Use for new projects, chaotic docs, or navigation issues.
Automates two-pass GTD inbox triage in Obsidian Markdown files: annotates unprocessed items with routing proposals, then routes reviewed items to projects based on user // comments.