now

Rebuilds per-project status snapshot files from recent diary entries.

Updated May 3, 2026
One-click install
npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill now-spikelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: now
Source: https://github.com/spikelab/multiplai-cc-mktplace/tree/main/plugins/multiplai-context/skills/now
Command: npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill now-spikelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Per-project now/<project>.md status snapshots injected at session start can become stale or incorrect after a diary backfill, edits to the project mapping config, or pipeline drift, leaving new sessions with an outdated picture of where each project stands. ## Core Features & Use Cases - Full snapshot rebuild: Regenerates every now/<project>.md file as a 3-5 bullet status synthesized from diary entries within a 48-hour lookback window. - Single-project rebuild: Targets one project by name via the --project flag when only one snapshot needs refreshing. - Graceful summarization fallback: Uses the configured model client for summaries, falling back to extractive truncated-snippet summaries when no client is available. - Use Case: After running a /multiplai-context:backfill of historical diary entries, run this skill so the SessionStart hook injects accurate, freshly synthesized project status into the next session. ## Quick Start Ask the assistant to rebuild all project status snapshots, optionally naming a single project to refresh just that one.

Frequently Asked Questions about now

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rebuild project status snapshots after a diary backfill?

Run the synthesize_now.py script via uv with no arguments for a full rebuild of all projects, or pass --project <name> to refresh a single project. The script regenerates now/<project>.md files from diary entries in the 48-hour lookback window.

Why are my project snapshots landing under the wrong project names?

Snapshot names come from the shared project-identity resolver in .multiplai/project-map.yaml, not from this skill. If snapshots appear under a subdirectory or 'workspace', revise the mapping by running /multiplai-context:setup.

What happens if no recent diary entries exist when rebuilding snapshots?

If no diary entries fall inside the 48-hour lookback window, the output directory ends up empty and no now/<project>.md files are written. The skill reports this so you know there was nothing recent to summarize.

Does snapshot summarization work without a configured model client?

Yes. Without a configured model client, the script falls back to an extractive summary built from truncated snippets. Both paths write the same now/<project>.md file shape, so downstream injection is unaffected.

When should I run a manual snapshot rebuild instead of the automatic pipeline?

The live pipeline refreshes each project's snapshot after writing its diary, so manual rebuilds are only needed after a backfill, after editing project-map.yaml, or to recover from stale or incorrect snapshots.