/work-log - Quick Activity Logger

Log completed work to the context database for future discovery by /work-next, handoffs, and session summaries.

System Prompt

EXECUTION DIRECTIVE: When the user invokes this command, you MUST:

1. Capture the work description provided
2. Add metadata (timestamp, files if mentioned, category)
3. Store in context database via /cx mechanism
4. Confirm the entry was logged

---

Usage

/work-log "description of work completed"
/work-log "Fixed cart API" --category bugfix
/work-log "Added user auth" --files "auth.ts,login.tsx"

Examples

# Simple log
/work-log "Implemented pricing calculator component"

# With category
/work-log "Fixed null pointer in checkout" --category bugfix

# With files modified
/work-log "Refactored auth flow" --files "auth.ts,useAuth.ts,Login.tsx"

# With related task
/work-log "Completed Track A.3 cart integration" --task "A.3"

# End of session summary
/work-log "Session complete: Cart API, type fixes, deployed v1.0.5" --session-end

What It Does

1. Captures work description with ISO 8601 timestamp
2. Extracts metadata (category, files, related tasks)
3. Stores in context DB for future queries
4. Updates session log if --session-end flag used

Entry Format

Entries are stored with this structure:

{
  "type": "work_log",
  "timestamp": "2026-01-03T12:30:00Z",
  "description": "Fixed cart API response mismatch",
  "category": "bugfix",
  "files": ["cart.service.ts", "useCart.ts"],
  "task_ref": "A.3",
  "session_id": "current-session-uuid"
}

Options

Option	Description
--category TYPE	Categorize: feature, bugfix, refactor, docs, test, deploy
--files LIST	Comma-separated list of files modified
--task REF	Link to task reference (e.g., "A.3", "PILOT-15")
--session-end	Mark as end-of-session summary
--importance HIGH/MED/LOW	Flag importance for /work-next

Categories

Category	When to Use
feature	New functionality added
bugfix	Bug or error fixed
refactor	Code restructuring, no behavior change
docs	Documentation updates
test	Test additions or fixes
deploy	Deployment or release activity
config	Configuration changes
research	Investigation or analysis

Integration

Logged work appears in:

• /work-next recommendations
• /handoff documentation
• /cxq queries
• Session summaries

Related Commands

Command	Relationship
/work-next	Consumes work logs for recommendations
/cx	Underlying context capture mechanism
/cxq	Query logged work
/handoff	Includes logged work in handoffs
/session-log	Detailed session logging (complementary)

Success Output

When work is logged successfully:

✅ COMMAND COMPLETE: /work-log
Entry: "description"
Timestamp: YYYY-MM-DDTHH:MM:SSZ
Category: <category>
Stored: context-storage

Completion Checklist

Before marking complete:

• Work description captured
• Timestamp generated (ISO 8601)
• Entry stored in context DB
• Confirmation displayed

Failure Indicators

This command has FAILED if:

• ❌ Context database unavailable
• ❌ Invalid category specified
• ❌ Write to context failed
• ❌ No confirmation displayed

When NOT to Use

Do NOT use when:

• Trivial work not worth tracking
• Already logging via /session-log (avoid duplicates)
• Work not completed (use for completed items)

Anti-Patterns (Avoid)

Anti-Pattern	Problem	Solution
Vague descriptions	Low value	Be specific about what was done
Skip category	Hard to filter	Use --category for better queries
Log incomplete work	Misleading history	Only log completed work

Principles

This command embodies:

• #9 Based on Facts - Records actual work done
• #6 Clear, Understandable - ISO timestamps, structured format
• #3 Complete Execution - Entry stored with metadata

Full Standard: CODITECT-STANDARD-AUTOMATION.md

---

Version: 1.0.0 Created: 2026-01-03 Author: CODITECT Team