/context:note

Append a timestamped note to the project context file.

Quick Start

Copy/context:note NOTE="Your note here"

Purpose

Quickly add a note to docs/context.md under the "Notes" section. Useful for recording:

• Decisions and rationale
• Observations during development
• Reminders for future sessions
• Team communications
• Technical discoveries

Parameters

Example Usage

Copy# Record a decision
/context:note NOTE="Decided to use JWT instead of sessions"
 
# Document an issue
/context:note NOTE="User reported auth bug in production, investigating"
 
# Sprint planning note
/context:note NOTE="Sprint planning: focusing on US-0042 and US-0045 this week"
 
# Technical discovery
/context:note NOTE="Performance issue fixed: reduced API response time by 40%"
 
# Stakeholder feedback
/context:note NOTE="Stakeholder meeting: new feature request added to backlog"

Note Format

Notes are appended with ISO 8601 timestamps:

Copy## Notes
 
- **[2024-12-31T10:30:00Z]**: Decided to use JWT instead of sessions
- **[2024-12-31T15:45:00Z]**: User reported auth bug in production
- **[2025-01-01T09:00:00Z]**: Sprint planning: focusing on US-0042 this week

Workflow

Step 1: Provide Note Text

If NOTE argument is missing, you'll be prompted:

What note would you like to add to docs/context.md?

Step 2: Diff-First Confirmation

Before writing, the command shows what will change:

Copy## Notes
 
- **[2024-12-31T10:30:00Z]**: Old note here
+ - **[2025-01-07T14:22:00Z]**: New note being added

Step 3: Confirm

You must approve the change before it's applied.

Auto-Creation

If docs/context.md doesn't exist

The command creates it with a Notes section:

Copy# Project Context
 
<!-- MANAGED_SECTION: placeholder -->
Run /agileflow:context:full to populate project context.
<!-- END_MANAGED -->
 
## Notes
 
- **[2025-01-07T14:22:00Z]**: Your note here

If Notes section doesn't exist

The command adds it at the end of the file:

Copy[existing content...]
 
## Notes
 
- **[2025-01-07T14:22:00Z]**: Your note here

Timestamp Format

All timestamps use ISO 8601 format (UTC):

YYYY-MM-DDTHH:MM:SSZ

Examples:

• 2024-12-31T10:30:00Z - correct
• 2025-01-07T15:45:30Z - correct

This ensures:

• Consistent sorting
• Universal time reference
• Machine-readable format
• Easy chronological ordering

Chronological Order

Notes appear in the order they were added:

• Oldest notes at the top
• Newest notes at the bottom

This provides a chronological history of decisions and discoveries.

Good Note Examples

Copy# Technical decisions
/context:note NOTE="Switched from REST to GraphQL for complex queries"
 
# Bug tracking
/context:note NOTE="Fixed race condition in user auth - PR #245"
 
# Team coordination
/context:note NOTE="API team ready for integration - contact @john"
 
# Environment changes
/context:note NOTE="Upgraded Node.js to v20 in CI - all tests passing"
 
# External dependencies
/context:note NOTE="Stripe API v2 deprecation - migrate by March 2025"

When to Use

• After making decisions - Document the reasoning
• When encountering issues - Track problems and solutions
• During planning - Record sprint goals and focus areas
• After deployments - Note version releases
• When blocked - Document blockers for context

Note vs ADR

For significant technical decisions, use /adr instead.

Viewing Notes

Notes are visible when you:

1. View docs/context.md directly
2. Run /context:export (if space allows)
3. Run /context:full to refresh context

Related Commands

• /context - Overview of context commands
• /context:full - Generate full context
• /context:export - Export concise excerpt
• /adr - Create architecture decision records