notetaker-fundamentals

Document AI-assisted development decisions with structured code annotations.

187|20|Updated Nov 20, 2025

Search Tags:#documentation #context #ai #TODO #notes #breadcrumbs

Ready to run

npx skills add https://github.com/TheBushidoCollective/han --skill notetaker-fundamentals

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: notetaker-fundamentals
Source: https://github.com/TheBushidoCollective/han/tree/main/jutsu/jutsu-notetaker/skills/note-taking-fundamentals
Command: npx skills add https://github.com/TheBushidoCollective/han --skill notetaker-fundamentals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill teaches structured note-taking for AI-assisted development, preserving rationale, alternatives, and context.

Core Features & Use Cases

AI development notes: Breadcrumbs for decisions and rationale.
Structured TODOs: Context-rich TODO comments for follow-up.
Decision records & uncertainty markers: Capture trade-offs and open questions.

Quick Start

Place an AI-DEV-NOTE above a complex function explaining why a caching strategy was chosen.

Frequently Asked Questions about notetaker-fundamentals

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

FAQPage Schema

How do I document decisions and context in code for AI assistants?▼

Leave structured AI development notes above complex functions and decision points. AI-DEV-NOTE annotations preserve rationale, trade-offs, and context—such as why a caching strategy was chosen—so AI tools and future developers understand the reasoning behind implementation choices without reconstructing it from git history.

What's the best way to write TODO comments that capture full context?▼

Structured TODOs go beyond task names: include the problem being deferred, related issues or PRs, and constraints or alternatives considered. This context-rich format helps AI assistants and team members understand not just what remains, but why it was deferred and what decision criteria apply.

Why should I mark uncertainty in code annotations?▼

Uncertainty markers signal unresolved questions, experimental approaches, or areas where trade-offs remain. They guide AI assistants to recognize unstable sections and avoid propagating assumptions downstream, improving traceability and enabling more informed refactoring decisions.

How do I link code notes to issues and pull requests?▼

Embed issue and PR references directly in AI development notes and enhanced TODO comments. Cross-linking creates breadcrumbs that connect code annotations to external context—requirements, discussions, and decisions—making the rationale discoverable without leaving the codebase.

Can I use consistent note formats across multiple programming languages?▼

Yes. The Skill enforces cross-language comment formats and proximity guidelines so annotations remain consistent whether you're writing Python, JavaScript, Go, or other languages. Standardized placement and syntax ensure AI tools and human readers find and interpret notes reliably.