# now-weekly-planning

> Manages weekly planning in the NOW system. View and track weekly outcomes, key tasks, meetings, and retrospectives. Triggers on: weekly outcomes, this week, weekly plan, week's goals, what's my focus this week, weekly review, retrospective.

- Author: Ravindra Barthwal
- Repository: ravindrabarthwal/life
- Version: 20260201123150
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/ravindrabarthwal/life
- Web: https://mule.run/skillshub/@@ravindrabarthwal/life~now-weekly-planning:20260201123150

---

---
name: now-weekly-planning
description: "Manages weekly planning in the NOW system. View and track weekly outcomes, key tasks, meetings, and retrospectives. Triggers on: weekly outcomes, this week, weekly plan, week's goals, what's my focus this week, weekly review, retrospective."
---

# NOW Weekly Planning

Manages weekly planning operations in the NOW task management system.

---

## ⚠️ CRITICAL NOTES

### 1. Domain Flag Position
The `-d` flag **MUST come BEFORE** the subcommand:
```bash
# ✅ Correct
./tools/now/bin/now -d work api outcomes

# ❌ Wrong - will not work!
./tools/now/bin/now api outcomes -d work
```

### 2. Read-Only API
There is **NO API for directly modifying** weekly outcomes. To add/edit:
- Use the CLI to open the file: `./tools/now/bin/now -d work week`
- Or edit the markdown file directly at: `{domain}/planning/weeks/{YYYY}-W{NN}.md`
- The API only provides **read-only access** via `api outcomes`

---

## CLI Location

All commands use: `./tools/now/bin/now`

## Quick Reference

| Action | Command |
|--------|---------|
| View weekly outcomes | `./tools/now/bin/now -d work api outcomes` |
| View both domains | `./tools/now/bin/now api outcomes --combined` |
| Open weekly file | `./tools/now/bin/now -d work week` |
| Show weekly plan | `./tools/now/bin/now week --show` |

---

## View Weekly Outcomes

```bash
# CLI (shows both domains)
./tools/now/bin/now week --show

# JSON API (single domain)
./tools/now/bin/now -d work api outcomes

# JSON API (both domains)
./tools/now/bin/now api outcomes --combined

# JSON API (specific week)
./tools/now/bin/now -d work api outcomes --date 2026-02-01
```

## Open Weekly File in Editor

```bash
./tools/now/bin/now -d work week
```

---

## Weekly File Location

`{domain}/planning/weeks/{YYYY}-W{NN}.md`

Example: `work/planning/weeks/2026-W05.md`

---

## Planning Hierarchy Context

```
Quarterly Goals (3 big goals)
    ↓
Monthly Focus Areas (3 focus areas + milestones)
    ↓
Weekly Outcomes (3 key outcomes)  ← This skill
    ↓
Daily Tasks (Critical + Regular + Carried)
```

Weekly outcomes should align with monthly focus areas and contribute to quarterly goals.

---

## Weekly File Sections

The weekly file contains:

1. **Outcomes (Top 3)** - Your key deliverables for the week
2. **Goals This Week** - Links to quarterly goals you're working on
3. **Key Tasks** - Important tasks organized by category
4. **Meetings** - Scheduled meetings with dates/times
5. **Blocked/Waiting** - Items that are stuck
6. **Retrospective** - End-of-week reflection (what worked, what didn't, what to change)

---

## Common Workflows

### When user asks "What are my weekly outcomes?"

```bash
./tools/now/bin/now -d work api outcomes
```

### When user asks "What should I focus on this week?"

```bash
./tools/now/bin/now -d work api outcomes
```

### When user asks "Show me everything for the week"

```bash
./tools/now/bin/now api outcomes --combined
```

### When user wants to update weekly outcomes

```bash
# Open the file to edit directly
./tools/now/bin/now -d work week
```

---

## API Response Format

All `api` commands return JSON:

```json
{
  "success": true,
  "data": { /* response data */ }
}
```

On error:

```json
{
  "success": false,
  "error": "Error message"
}
```