Document completed work and decisions using /docent:tell entries.
npx skills add https://github.com/tnez/docent --skill capture-work-guidance
Please help me install this Agent Skill. Skill: capture-work-guidance Source: https://github.com/tnez/docent/tree/main/skills/docent/capture-work-guidance Command: npx skills add https://github.com/tnez/docent --skill capture-work-guidance
AI agents often complete tasks without adequately documenting their work, leading to knowledge gaps and repeated effort. This Skill provides comprehensive guidance for AI agents on when and how to proactively capture documentation using /docent:tell, transforming ephemeral work into persistent, searchable knowledge.
Explain how to proactively capture documentation using /docent:tell.
High-intent search queries and answers about installing and using this skill.
Proactive documentation captures work using `/docent:tell` at critical moments: after completing tasks, making decisions, discovering insights, hitting blockers, and at natural breakpoints. This creates persistent, searchable knowledge that persists across sessions instead of losing context when work ends.
Document at five critical moments: task completion, key decisions, valuable insights discovered, blockers encountered, and natural workflow breakpoints. Capturing at these specific points ensures context-rich rationale is preserved rather than forgotten, preventing repeated effort and knowledge gaps.
Effective documentation explains the 'why' behind decisions with specific context, not just what was done. Structure entries with decision rationales, discovered insights, and blockers using standardized formatting. Avoid anti-patterns like deferring documentation or assuming context is obvious to future reference.
Structured `/docent:tell` entries create persistent memory across sessions, allowing seamless context switching and future reference. Documenting decisions, insights, and blockers immediately after discovery transforms ephemeral work into searchable knowledge that survives task completion and session boundaries.
Yes. This guidance applies across software projects to document post-work summaries, decision rationales, and discovered insights. It ensures every key decision and completion during feature development automatically creates rich, persistent working memory for future reference and context switching.
Snowflake-LabsA concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略
viraatdasIndexes and searches project learnings from learnings.jsonl and plan logs.
RobbyMo81Coordinate multi-agent workflows in OpenProse with sessions, imports, and state backends for parallel execution and persistence.
devkadeAggregate Obsidian weekly notes into a structured monthly summary.
