ado-workplan

Files (7)

• README.md
• SKILL.md
• ARCHITECTURE.md · docs/
• EXAMPLES.md · docs/
• OPERATIONS-AND-TESTING.md · docs/
• REFERENCE.md · docs/
• WORKFLOW.md · docs/

SKILL.md (first lines)

# ADO Workplan Generator (Sprint Tasks Only)

Generates a formatted, time-blocked workplan for **ADO sprint work only** — PBIs, tasks, code reviews, and engineering work.

> **This skill does NOT include IcM/DRI duties.** For livesite work use `dri-workplan`. For combined output use `dayplan`.

## 🛑 CRITICAL RULES — DATE & TIME

- **DATE**: MUST be fetched from the internet (use a web tool). Must be accurate as per **IST (India Standard Time, UTC+5:30)**. NEVER guess the date.
- **TIME**: When workplan is requested, it should **start from current time** — show only remaining time blocks from now until 18:00 IST. Skip blocks that have already passed.
- **Current time** displayed anywhere in the output MUST always be in **IST**.

## Previous-day completion reconciliation (mandatory)

Standing user preference, 2026-09-17: always read yesterday's actual sprint note to see what the user marked complete.

1. Before planning, read yesterday's daily Markdown file from the existing Zettelkasten sprint folder, plus today's file if present. If yesterday's file is absent, use the most recent preceding note and state its actual date. Follow existing folder names (for example, `SPRINT_SEPT_26`), not a newly invented alternate spelling.
2. Treat checked `[x]` / `[X]` actions as user-recorded completion evidence for their stated scope. Carry forward only unfinished actions; never reset checked actions, recreate tasks the user removed from the note, or copy a whole checklist blindly. For partial completion, retain the unfinished children without reopening completed siblings.
3. Reconcile with live ADO status. Exclude Done/Closed/Removed items from pending work. If note and ADO status disagree, describe the discrepancy; do not change ADO state merely because a checkbox was checked.
4. Keep yesterday's note, evidence tables, and checkmarks untouched. If showing prior completion, label it "Completed yesterday" or use the actual source date, never "Completed today." Do not infer a deletion/rollout occurred when that action remains unchecked.
5. Preserve existing Obsidian `[[wikilinks]]`, link today's note to the carry-forward source, and add today's return link to the relevant `2 Areas` topic notes. If today's note already exists, preserve its edits/checkmarks and deduplicate by ADO ID and action.

## When to use this skill

- User asks for "workplan", "daily plan", "schedule", "what's on my plate"
- User asks "show plan", "updated plan", "gimme workplan"
- Morning start or afternoon refresh requests
- Any request to summarize today's ADO/sprint work

## Data Sources

1. **ADO MCP** — `ado-msazure-wit_my_work_items` or `ado-msazure-wit_get_work_items_batch_by_ids` for active sprint tasks
2. **Session SQL** — `user_preferences` table for schedule, display rules, and formatting
3. **Session SQL** — `work_items` table for cached item state
4. **Zettelkasten daily notes** — yesterday's actual user-edited checklist and today's existing note, read before scheduling. If optional SQL tables are unavailable, use persisted WorkDesk preferences rather than inventing cached state.

## User Preferences (from SQL)

Always read these before rendering:

| Key | Purpose |
|-----|---------|
| `daily_routine` | Work hours and time blocks (11:00–18:00 IST) |
| `workplan_style` | Exact visual format specification |
| `ado_display_rule` | PBI/Task hierarchy display rules |

## Output Format

Uses the **shared two-column box layout** (same as dri-workplan and dayplan).

### Structure

```
 ┌───────────────────────────────────────────────────────────┐
 │  📋 ADO WORKPLAN — {Day}, {Date}                          │
 │  🕚 Hours: 11:00–18:00 IST                                │
 │  🔵 Active: {count} │ 🔍 In Review: {count}               │
 ├───────────┬──────────────────────────────────────────────┤
 │           │                                              │
 │ HH:MM     │ {emoji} Block Title                          │
 │           │  ➤ Sub-item detail                          │
 │           │                                              │
 │- - - - - -│- - - - - - - - - - - - - - - - - - - - - - - │
```

 - {status_emoji} [#{id}](url) — Task title

```
 │           │                                             │
 ├───────────┴─────────────────────────────────────────────┤
 │  💡 Insight or tip line                                 │
 │  📌 QUEUED                                              │
```

 - ⬚ [#{id}](url) — Queued item title

```
 └─────────────────────────────────────────────────────────┘
```

### Key Rules

1. **Box inside code fences** — preserves monospace alignment
2. **Lines kept SHORT (~55 chars)** — avoids terminal wrapping
3. **Two-column**: time │ content with emoji
4. **Dashed separators**: `│- - - - - -│- - - - - - - - -│`
5. **Sub-items**: `➤` prefix inside box
6. **Links as markdown bullets OUTSIDE code fences** — between box segments so they're clickable
7. **Multiple code fence blocks** broken up by link bullets
8. **Footer** with 💡 tip + 📌 QUEUED section
9. **Closing `└───┘`** in its own code fence after queued links

### Link Emoji Legend

| Emoji | Meaning |
|-------|---------|
| 🔵 | Active ADO task (In Progress) |
| 🔍 | In Review ADO task |
| ⬚ | Queued / To Do / low-priority |
| 🅿️ | Parked / Committed but not started |
| ✅ | Done (only shown in "completed today" section) |

### URL Format

- **ADO**: `https://msazure.visualstudio.com/One/_workitems/edit/{id}`

### ADO Display Rules

- If PBI has child tasks → show PBI as header, tasks nested below with `├─` / `└─`
- If PBI has NO child tasks → show PBI standalone
- Only `#number` is hyperlinked, title is plain text after em-dash

## Schedule Template (IST) — Sprint Blocks

| Time | Block |
|------|-------|
| 11:00 | 🟢 Start Day — email/Teams triage |
| 11:30 | 🔵 Standup (Yesterday/Today/Blocker format) |
| 12:00 | 🟣 Focus Block 1 — high-priority tasks |

From Zanark/skill-library, Apache-2.0.

More from Zanark/skill-library