prime-feat
Prime Feature Context
Load all planning artifacts and context for feature {{feature_number}}.
Artifact Locations
- Find the feature folder: check
backlog/plans/{{feature_number}}-*/first, thenbacklog/plans/_completed/{{feature_number}}-*/ - Read all planning documents:
- analysis.md
- spec.md
- research.md
- plan.md
- data-model.md
- tasks.md
- contracts/ (all files)
- Read spec tests:
specs/tests/{{feature_number}}-*.md - Check git branch status for
feature/{{feature_number}}-*
Workflow
- Check
backlog/plans/first for in-progress features, thenbacklog/plans/_completed/for completed ones - Use
ls backlog/plans/ backlog/plans/_completed/to find the folder matching{{feature_number}}-* - Once found, extract the full feature ID (e.g.,
001-mcp-integration) and path - Read all files in
{feature-path}/:- Start with
analysis.md,spec.md,plan.md(core docs) - Then
data-model.md,tasks.md,research.md - Finally list and read files in
contracts/directory
- Start with
- Read
specs/tests/{feature-id}.mdif it exists - If
.ainotes/memory.mdexists, read it for accumulated agent context - Run
git statusandgit branch --show-currentto check current branch - If not on the feature branch, suggest:
git checkout feature/{feature-id} - Analyze
tasks.mdand summarize:- Total task count
- Completed count (checked boxes)
- Current phase based on task completion
- Next uncompleted task
Output Summary
Present a concise status report in this format:
┌─────────────────────────────────────────────────────────────┐
│ Feature {NNN}-{slug} │
├─────────────────────────────────────────────────────────────┤
│ Branch: feature/{NNN}-{slug} ✓ (or ✗ if not on branch) │
│ Progress: {completed}/{total} tasks ({percent}%) │
├─────────────────────────────────────────────────────────────┤
│ Phase Progress: │
│ Phase 1: {name} ████████████ {done}/{total} ✓ │
│ Phase 2: {name} ██████░░░░░░ {done}/{total} ← current │
│ Phase 3: {name} ░░░░░░░░░░░░ {done}/{total} │
│ ... │
├─────────────────────────────────────────────────────────────┤
│ Recently Completed: │
│ • T{N} - {description} │
│ • T{N} - {description} │
├─────────────────────────────────────────────────────────────┤
│ Next Up: │
│ → T{N} - {description} ← START HERE │
│ T{N} - {description} │
│ T{N} - {description} │
└─────────────────────────────────────────────────────────────┘
Report Guidelines
- Phase Progress: Show all phases with a visual progress bar (█ for done, ░ for remaining)
- Recently Completed: Show last 2-3 completed tasks from the current phase
- Next Up: Show next 3 uncompleted tasks, marking the first with "← START HERE"
- Keep it scannable: Use consistent formatting, avoid prose
Progress Bar Calculation
For each phase, calculate: done / total * 12 filled blocks (█), remainder as empty (░)
Important: Do NOT provide a detailed summary of the documents - they are already loaded into context. The report replaces verbose explanations.
More from ianphil/my-skills
astral-uv
>
11glab
GitLab CLI (glab) for merge requests, issues, and CI/CD pipelines. Use when working with GitLab repositories for MR creation/review, issue management, pipeline debugging, or any GitLab API operations. Triggers on GitLab URLs, mentions of "merge request" or "MR" (not "PR"), gitlab.com, or glab commands.
10workiq
This skill should be used when the user asks to "install WorkIQ", "set up WorkIQ", "query my emails with AI", "connect AI to Microsoft 365", "query my meetings or documents", "use workiq ask", or wants to use natural language to search Microsoft 365 data (emails, meetings, Teams messages, documents, people) from an AI assistant.
1closer
This skill should be used when the user asks to "close feature", "archive feature", "complete feature N", "move feature to completed", or wants to move a finished feature to the _completed/ directory.
1tmux-tdd
Interact with tmux-based TDD environments. Use when running tests in tmux panes, checking test output, parsing test failures, or orchestrating TDD workflows. Works with any language (Rust, Python, JavaScript, Go, etc). Read test output directly from tmux panes.
1quick-plan
This skill should be used when the user asks to "create a quick plan", "draft a plan", "capture this idea", "plan this feature", or wants a lightweight plan without full feature planning. Creates concise plans in backlog/plans/ for later expansion.
1