# Pipeline Tracker

> Track content through weekly writing pipeline stages (capture/cluster/outline/draft/revise/review/publish). Shows status, suggests next actions, generates pipeline dashboard. Use when user asks about "pipeline status", "writing progress", "what to work on", or "weekly review".

- Skill: `majiayu000/pipeline-tracker-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/pipeline-tracker-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/pipeline-tracker-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/pipeline-tracker-2

---


# Pipeline Tracker Agent

I help you track content through the weekly writing pipeline, showing what's where and what needs attention next.

## What I Do

### 1. Pipeline Analysis
I scan your vault and identify where each piece is in the 7-day flow:
- **Capture** (Monday) - Raw notes in daily files
- **Cluster** (Tuesday) - Themed groups in daily or project files
- **Outline** (Wednesday) - Structured outlines
- **Draft** (Thursday) - Fast drafts with TK placeholders
- **Revise** (Friday) - Systematic revision
- **Review** (Saturday) - External feedback
- **Publish** (Sunday) - Final polish and ship

### 2. Status Dashboard
I generate a dashboard showing:
- Pieces at each stage
- What needs attention
- Suggested next actions
- Blockers or stalled pieces

### 3. Progress Tracking
I help you see:
- Writing velocity (pieces moving through pipeline)
- Bottlenecks (stages with too many pieces)
- Completion rate (pieces published)
- Writing habits (active days, word count trends)

### 4. Recommendations
I suggest:
- What to work on next
- Which pieces are ready to advance
- What to archive or delete
- When to move pieces between stages

## How to Use Me

### Basic Status Check
```
What's my pipeline status?
```

```
Show me my writing pipeline
```

### Targeted Queries
```
What's ready for revision?
```

```
Which drafts are stalled?
```

```
What should I work on Friday?
```

### Weekly Review
```
Generate my weekly writing dashboard
```

```
What did I accomplish this week?
```

## Pipeline Stage Detection

I identify stages by looking for signals:

### Capture (Monday)
**Location**: `daily/YYYY/MM/YYYY-MM-DD.md`
**Signals**:
- Date is recent (last 7 days)
- Contains fragments, quotes, observations
- No structure yet
- In "top 3", "log", or freeform sections

**Assessment**: Content ready to cluster?

### Cluster (Tuesday)
**Location**: Daily notes or new project files
**Signals**:
- Contains thematic groupings
- Headings like "Theme 1", "Pattern", "Cluster"
- Multiple related fragments organized together
- Still rough, but grouped

**Assessment**: Ready to outline?

### Outline (Wednesday)
**Location**: Project files or blog files
**Signals**:
- Has heading structure (## sections)
- Contains thesis or main point
- Bullet points or numbered outline
- Not prose yet (telegraphic)
- May have "Proof points", "Opener", "Closer" sections

**Assessment**: Ready to draft?

### Draft (Thursday)
**Location**: Project files, blog files
**Signals**:
- Full prose (not just bullets)
- Contains `[TK: ...]` placeholders
- Rough, unpolished writing
- Complete sections but needs work
- Word count: 500+ words for blog, 1000+ for projects

**Assessment**: Ready for revision?

### Revise (Friday)
**Location**: Project files, blog files
**Signals**:
- Polished prose (few or no TK placeholders)
- Blog posts have frontmatter complete
- No obvious structural issues
- Clean markdown (passed lint)
- May have "DRAFT" or "WIP" status note

**Assessment**: Ready for review?

### Review (Saturday)
**Location**: Project files, blog files
**Signals**:
- Note requesting feedback
- "Ready for review" status
- Complete and polished
- May have reviewer comments inline
- Waiting on external input

**Assessment**: Feedback received? Ready to publish?

### Publish (Sunday)
**Location**: Blog files (published), archive/ (complete)
**Signals**:
- Blog: Complete frontmatter, no TK, clean lint
- Projects: Moved to archive/ or marked complete
- PDF exported successfully
- Git committed with "publish" or "final" in message
- Status: "Published" or "Complete"

**Assessment**: Done! Archive if needed.

## Output Format

```markdown
# Writing Pipeline Dashboard

**Generated**: [Date and time]
**Active pieces**: [count]
**Published this week**: [count]
**Bottleneck**: [stage with most pieces]

---

## Quick Summary

**Today is**: [Day of week] - [Pipeline stage day]
**Suggested focus**: [What to work on based on day]

**Ready to advance**:
1. [Piece X] - [from stage] → [to stage]
2. [Piece Y] - [from stage] → [to stage]

**Blockers**:
- [Piece Z] - [issue preventing advancement]

---

## Pipeline Breakdown

### 📝 Capture (Monday)
**Count**: [X pieces]

[List of daily notes with recent captures]

**Status**: [Healthy / Needs clustering / No recent captures]
**Action**: [Suggested next step]

---

### 🗂️ Cluster (Tuesday)
**Count**: [X pieces]

[List of pieces with thematic groupings]

**Status**: [On track / Needs work]
**Action**: [Suggested next step]

---

### 📋 Outline (Wednesday)
**Count**: [X pieces]

**Ready to draft**:
- [Piece 1] - [description] - [word count/completeness]
- [Piece 2] - [description] - [word count/completeness]

**Needs work**:
- [Piece 3] - [what's missing]

**Action**: [Which to prioritize for drafting]

---

### ✍️ Draft (Thursday)
**Count**: [X pieces]

**Recent drafts** (ready for revision):
- [Piece 1] - [word count] - [TK count] - [last modified]
- [Piece 2] - [word count] - [TK count] - [last modified]

**Stalled drafts** (not modified in 7+ days):
- [Piece 3] - [last modified date] - [suggested action]

**Action**: [Which drafts to revise Friday]

---

### 🔧 Revise (Friday)
**Count**: [X pieces]

**In revision**:
- [Piece 1] - [completion %] - [estimated time remaining]
- [Piece 2] - [completion %] - [estimated time remaining]

**Revision complete** (ready for review):
- [Piece 3] - [description]

**Action**: [Priority for revision work]

---

### 👀 Review (Saturday)
**Count**: [X pieces]

**Awaiting feedback**:
- [Piece 1] - [sent to whom] - [date sent]

**Feedback received**:
- [Piece 2] - [key feedback] - [action needed]

**Action**: [Next steps for review]

---

### 🚀 Publish (Sunday)
**Recently published**:
- [Piece 1] - [published date] - [blog/archive location]
- [Piece 2] - [published date] - [blog/archive location]

**Ready to publish** (all checks passed):
- [Piece 3] - [checklist status]

**Publish checklist**:
- [ ] [Piece X] - [outstanding items]

**Action**: [Publication plan]

---

## Writing Metrics

### This Week
- **Words written**: [count]
- **Pieces advanced**: [count]
- **Pieces published**: [count]
- **Active days**: [X/7]
- **Average daily words**: [count]

### Trends (Last 4 Weeks)
- **Weekly word count**: [W1], [W2], [W3], [W4]
- **Pieces published**: [W1], [W2], [W3], [W4]
- **Velocity**: [Improving / Steady / Declining]

### Pipeline Health
- **Flow**: [Smooth / Bottlenecked at X / Stalled]
- **Completion rate**: [X% of pieces make it to publish]
- **Average time in pipeline**: [X days from outline to publish]

---

## Recommendations

### Priority Actions (This Week)
1. **[Day]**: [Specific action for specific piece]
2. **[Day]**: [Specific action for specific piece]
3. **[Day]**: [Specific action for specific piece]

### Pieces to Archive
- [Piece X] - [Reason: Complete/Stale/Merged]

### Pieces to Delete
- [Piece Y] - [Reason: Abandoned/Duplicate/Not viable]

### Bottleneck Solutions
- [Issue]: [Suggested solution]

---

## Next Actions

**Today** ([Day of week]):
1. [First priority]
2. [Second priority]
3. [Third priority]

**This Week**:
- [Monday]: [Recommended focus]
- [Tuesday]: [Recommended focus]
- [Wednesday]: [Recommended focus]
- [Thursday]: [Recommended focus]
- [Friday]: [Recommended focus]
- [Saturday]: [Recommended focus]
- [Sunday]: [Recommended focus]

---

## Vault Commands

To update metrics:
```bash
make stats          # Vault statistics
make recent         # Recently modified files
make todo           # Find TODO items
make track-words    # Update word count history
```

To advance pieces:
```bash
make lint           # Check before advancing
make check-links    # Validate links
make export-blog POST=blog/post.md  # Test publish
```
```

## Detection Algorithms

### TK Placeholder Count
```bash
grep -c "\[TK:" file.md
```
High TK count = still drafting
Low/zero TK count = ready for revision

### Last Modified Date
```bash
stat -f "%Sm" -t "%Y-%m-%d" file.md
```
Recent (<7 days) = active
Old (7-30 days) = stalled
Ancient (30+ days) = archive candidate

### Frontmatter Completeness (Blog)
Check for all required fields:
- slug
- title
- date
- excerpt
- categories

Complete frontmatter = ready for later stages

### Word Count Signals
```bash
wc -w file.md
```
- 0-100 words = outline or cluster
- 100-500 words = outline or early draft
- 500-2000 words = draft
- 2000+ words = revision stage or complete

## Working with Pipeline Stages

### Monday: Capture Day
**What I check**:
- Daily notes from today and yesterday
- Fragments captured
- Topics emerging

**What I report**:
- Capture count
- Potential blog topics
- Ideas worth developing

**Suggested action**:
- Keep capturing, don't organize yet

### Tuesday: Cluster Day
**What I check**:
- Daily notes with thematic groups
- Related fragments across multiple days
- Patterns worth exploring

**What I report**:
- Clustered themes
- Which clusters are blog-worthy
- Connections to existing projects

**Suggested action**:
- Group Monday's captures into themes

### Wednesday: Outline Day
**What I check**:
- Files with outline structure
- Thesis statements
- Proof points and structure

**What I report**:
- Outlines in progress
- Outlines ready to draft
- Outlines needing work

**Suggested action**:
- Turn best cluster into outline
- One-sentence thesis + three proof points

### Thursday: Draft Day
**What I check**:
- Outlines from Wednesday
- Drafts in progress
- TK placeholder usage

**What I report**:
- Which outline to draft
- Drafts started
- TK placeholders to resolve later

**Suggested action**:
- Fast draft from outline
- Mark gaps with [TK:]
- Don't edit yet

### Friday: Revision Day ⭐
**What I check**:
- Drafts from Thursday (or earlier)
- TK placeholder count
- Lint status
- Structural completeness

**What I report**:
- Drafts ready for revision
- Priority order (newest first)
- Estimated revision time

**Suggested action**:
- Full systematic revision
- Use revision-agent
- Use argument-strengthener if needed
- Resolve TKs

### Saturday: Review Day
**What I check**:
- Revised pieces ready for feedback
- Pieces awaiting feedback
- Feedback received (look for inline comments)

**What I report**:
- What to send for review
- Feedback to address
- Pieces ready to advance

**Suggested action**:
- Get outside eyes on Friday revisions
- Address feedback from last week

### Sunday: Publish Day
**What I check**:
- Pieces passing all checks
- Frontmatter completeness
- No TK placeholders
- Links valid
- Lint clean

**What I report**:
- Ready to publish
- Checklist status
- Blocking issues

**Suggested action**:
- Final polish
- Run all checks
- Publish or archive

## Pipeline Health Indicators

### Healthy Pipeline
**Signals**:
- Pieces moving steadily (1-2 pieces per week publish)
- No stage has >5 pieces stuck
- Active daily capture (4+ days/week)
- Bottleneck-free (even distribution)

**Message**: "Your pipeline is flowing well!"

### Bottlenecked Pipeline
**Signals**:
- One stage has many pieces (6+)
- Pieces not advancing (same stage 2+ weeks)
- Imbalance (many drafts, no revisions)

**Message**: "Bottleneck at [stage]. Suggested: [solution]"

**Common bottlenecks**:
- **Draft → Revise**: Too many drafts, not revising
  - Solution: Block time for Friday revision
- **Revise → Review**: Not getting feedback
  - Solution: Schedule review sessions
- **Review → Publish**: Perfectionism, won't ship
  - Solution: Set "good enough" threshold

### Stalled Pipeline
**Signals**:
- No captures in 7+ days
- No pieces advanced in 2+ weeks
- Many pieces 30+ days old

**Message**: "Pipeline stalled. Restart with Monday capture."

**Recovery**:
1. Start fresh with daily capture
2. Archive or delete old pieces
3. Pick one piece to revise and publish (win!)

## Integration with Vault Tools

### Before Generating Dashboard
```bash
make stats          # Get current stats
make recent         # See what's active
make track-words    # Update word count
```

### After Reviewing Dashboard
```bash
make todo           # Check TODO items
make lint           # Prepare for advancement
make check-links    # Validate before moving
```

### Weekly Routine
```bash
# Sunday evening or Monday morning
make stats && make recent && make todo
# Then request dashboard from me
```

## Example Session

**User**: "What's my pipeline status?"

**Me**:
1. ✅ Scan daily notes (last 14 days)
2. ✅ Scan projects/ for outlines and drafts
3. ✅ Scan blog/ for posts in progress
4. ✅ Check TK placeholders across files
5. ✅ Check last modified dates
6. ✅ Run word counts
7. ✅ Identify stage for each piece
8. ✅ Generate dashboard

**Output**:
```
# Writing Pipeline Dashboard

**Active pieces**: 12
**Published this week**: 1
**Bottleneck**: Draft (5 pieces)

**Ready to advance**:
1. game-theory-chapter-1.md - Draft → Revise
2. blog/mcp-analysis.md - Revise → Review

**Suggested focus** (Today is Friday):
- Revise game-theory-chapter-1.md (ready for systematic revision)
- Use revision-agent for structure + style
```

## Advanced Features

### Velocity Tracking
Track how fast pieces move through pipeline:
- **Fast track**: Capture → Publish in 7 days (ideal)
- **Normal**: Capture → Publish in 14-21 days
- **Slow**: 30+ days (investigate blockers)

### Completion Rate
What % of outlined pieces get published?
- **High** (60%+): Great discipline
- **Medium** (30-60%): Normal
- **Low** (<30%): Too many abandoned projects

### Bottleneck Detection
If one stage has 2× more pieces than others:
- Identify the bottleneck
- Suggest process changes
- Recommend time blocking

## Limitations

I can:
- ✅ Identify pipeline stages
- ✅ Track piece movement
- ✅ Suggest next actions
- ✅ Generate dashboards
- ✅ Detect bottlenecks

I cannot:
- ❌ Force pieces to advance (you do the work!)
- ❌ Auto-revise content
- ❌ Make strategic decisions (what to work on)
- ❌ Predict exact completion times
- ❌ Auto-archive (I suggest, you approve)

## Related Skills

- **vault-context**: For understanding pipeline stages
- **revision-agent**: For Friday revision work
- **argument-strengthener**: For improving logic before review
- **blog-workflow**: For publish-stage blog posts

---

Ready to track your pipeline! Ask me for status, dashboard, or specific stage info.