Structures plan, context, and task documents per development task.
npx skills add https://github.com/ssiumha/dots --skill dev-docs
Please help me install this Agent Skill. Skill: dev-docs Source: https://github.com/ssiumha/dots/tree/main/prompts/skills/dev-docs Command: npx skills add https://github.com/ssiumha/dots --skill dev-docs
This Skill addresses the challenge of losing context during large or complex development tasks, especially when switching between projects or resuming work after a break. It ensures that all relevant information—plans, architectural notes, decisions, and tasks—is systematically captured and easily retrievable, boosting developer productivity and reducing cognitive load.
plan.md (goals, steps, risks), context.md (key files, architectural notes, decisions), and tasks.md (checklists, blockers). Use it when starting a new feature or tackling a complex bugfix to keep all details organized.Start a new dev-docs task for 'feature-user-profile-avatar-upload', and outline the main goals and phases.
High-intent search queries and answers about installing and using this skill.
Maintain development context by structuring tasks into three linked documents: plan.md for goals and phases, context.md for architectural notes and key files, and tasks.md for checklists and blockers. This triplet workflow captures and persists critical information so you can resume work after switching projects or taking a break without cognitive overhead.
Organize development documentation using a three-document structure per task under project directories with kebab-case naming. Frontmatter and templates enforce consistency, enabling automated lifecycle management from task start through archival and integration with your project knowledge base.
Structure task context with plan.md, context.md, and tasks.md documents that capture goals, architectural decisions, key files, and progress. This systematic capture enables another developer to quickly re-engage with your work, reducing handoff friction and ensuring nothing is lost.
Yes. This workflow enables seamless integration with Living Docs, allowing you to promote completed task knowledge—such as architectural patterns and significant decisions—into your permanent project knowledge base upon task completion.
When starting a feature or bugfix, document goals and phases in plan.md, capture architectural notes and key files in context.md, and outline task checklists with blockers in tasks.md. This structured approach keeps all details organized and retrievable throughout development.
Teams lose context when switching between projects or resuming after breaks because critical information—plans, decisions, and task status—scatters across tools. A three-document workflow with systematic capture and retrieval prevents this loss and reduces developer cognitive load.
AribSudiaScaffold wave directories and dispatch architectural and planning agents.
nexus-a1Archive completed requirements into a git-backed knowledge base with a searchable index.
RogerioSobrinhoCapture recurring patterns and architectural decisions into explicit standards.
DaddyElonMusk69Create and maintain an interlinked markdown knowledge base with YAML frontmatter.