Record structured implementation notes with verification status after task completion.
npx skills add https://github.com/davidlee/spec-driver --skill notes-davidlee
Please help me install this Agent Skill. Skill: notes Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/notes Command: npx skills add https://github.com/davidlee/spec-driver --skill notes-davidlee
This Skill solves the problem of losing critical implementation context after a task or phase ends, which forces future agents to rediscover decisions and pitfalls.
Use this Skill to record implementation notes immediately after finishing your work by asking the agent to add concise details about what was done, open questions, and any verification status.
High-intent search queries and answers about installing and using this skill.
To capture implementation notes for future agents, record concise, structured details about completed tasks, including durable facts, surprises, follow-ups, open questions, commit hashes, and verification status.
Spec-driven development implementation notes should include durable facts, surprises or adaptations, follow-up actions, open questions, commit references, pending work status, and whether verification succeeded.
You need to record verification status and commit references when a task or phase completes, ensuring future agents retain critical context for continuity and repairability without rediscovering decisions.
Record durable facts and follow-up actions after finishing a development phase by asking the agent to add concise, structured details about what was done, open questions, and any verification status.
Yes, you can locate the right card or location for implementation notes via the project's repository-aware discovery tooling when you are unsure where to store them.
Yes, capturing implementation notes works without external dependencies, requiring only concise, structured note content to flag reusable patterns and gotchas for later agents.
wise-clawLoad Wise task context and architectural constraints before code modification.
droxeyConvert meeting transcripts into summaries with decisions, owners, and tentative due dates.
neelbaumanManage the software development lifecycle through six sequential phases.
nyldnTranslate multi-AI research into a structured NLSpec with frontmatter metadata.
