How this command is triggered — by the user, by Claude, or both
Slash command
/project-tracker:log-sessionThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Log Work Session Create a session log documenting work done on an initiative. ## Instructions 1. **Identify the initiative**: - If slug provided, use it - Otherwise, list active initiatives and ask which one - Look in `$PROJECT_TRACKER_WORKSPACE/initiatives/active/` first, then `backlog/` 2. **Gather session details**: - Brief description (becomes filename and title) - What was completed - Any decisions made - Blockers or open questions - Next steps - Files changed (optional) - Git branch (optional) 3. **Create the session file** at: `$PROJECT_TRACKER...
Create a session log documenting work done on an initiative.
Identify the initiative:
$PROJECT_TRACKER_WORKSPACE/initiatives/active/ first, then backlog/Gather session details:
Create the session file at:
$PROJECT_TRACKER_WORKSPACE/initiatives/{state}/{slug}/sessions/{YYYY-MM-DD}-{description}.md
---
date: '{today's date YYYY-MM-DD}'
branch: {branch if provided}
---
# {description}
## Context
{Why this session was needed - can be brief}
## Completed
- [x] {completed item 1}
- [x] {completed item 2}
## Decisions Made
- {decision 1}
## Blockers / Open Questions
- {blocker if any}
## Next Session
- [ ] {next step 1}
- [ ] {next step 2}
## Files Changed
- `{file1}`
- `{file2}`
User runs: /log-session user-auth
You ask about what was accomplished, decisions, next steps...
You create: $PROJECT_TRACKER_WORKSPACE/initiatives/active/user-auth/sessions/2026-01-05-jwt-implementation.md
npx claudepluginhub p/hhopkins95-project-tracker-plugins-project-tracker-2/saveSaves a session log with what was done, decisions made, and pending items. Infers description from git history and conversation. Optionally commits and pushes.
/file-sessionWrites a rich session minute to the logbook: captures intent, decisions, changed files, and open threads. Enriches existing stubs or creates new entries.
/diaryCreates or updates a daily session diary entry documenting development progress, key decisions, and handoff context for the current date.
/logCreates a structured technical session log with context, decisions, work performed, outcomes, and next steps. Prompts for session details and generates searchable tags.
/taskview-logLogs the work completed in the current Claude Code session as a TaskView task, summarizing accomplishments, selecting a project, and creating the task with optional subtasks and tags.
/sessionlogSaves a structured session transcript to a markdown file, capturing key decisions, commands, problems, and resolutions for knowledge preservation across sessions.