dev-context

Create GitHub issue working spaces and Architecture Decision Records with file paths.

1|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/mpazaryna/claude-toolkit --skill dev-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-context
Source: https://github.com/mpazaryna/claude-toolkit/tree/main/generated-skills/dev-context
Command: npx skills add https://github.com/mpazaryna/claude-toolkit --skill dev-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates context switching and documentation overhead by providing structured workspaces for development tasks and architectural decisions.

Core Features & Use Cases

  • Issue Working Space: Creates organized folders with README, plan, and notes for GitHub issues and features.
  • Architecture Decision Records: Generates formal ADR documentation for major technical decisions.
  • Use Case: When starting work on GitHub issue #115, use this Skill to automatically create a dedicated workspace with implementation plan and tracking documents.

Quick Start

Use the dev-context skill to set up a working space for GitHub issue #115.

Frequently Asked Questions about dev-context

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

FAQPage Schema
How do I set up a structured workspace for a GitHub issue?

Create an Issue Working Space by applying dev-context to your GitHub issue number. The Skill generates a dedicated folder structure (docs/issues/{num}-{short-name}/) with README.md, plan.md, and notes.md files, eliminating manual setup and providing immediate scaffolding for implementation planning and progress tracking.

What is an Architecture Decision Record and when should I create one?

An Architecture Decision Record (ADR) documents major technical decisions with formal structure and numbering. Use dev-context to generate ADRs (docs/adr/NNN-{decision-name}.md) when you need to capture design rationale, alternatives considered, and consequences for future team reference.

How do I reduce context switching during development workflow?

dev-context eliminates context switching by creating centralized, template-driven workspaces for each task. Your issue or architectural decision gets dedicated documentation with status metadata, implementation plan, and notes in one location, keeping all relevant context within reach.

Can I use this Skill with GitHub issue tracking?

Yes. dev-context integrates directly with GitHub issue workflows. Trigger it with an issue number to automatically create an organized working space that links issue tracking to your local documentation structure.

What files does dev-context generate for a new feature?

For GitHub issues and features, dev-context generates three files: README.md (overview), plan.md (implementation strategy), and notes.md (progress tracking). All files are organized in a numbered, named folder within docs/issues/.

Do I need any dependencies or setup to use dev-context?

No external dependencies are required. dev-context works with your existing GitHub repository structure. It creates files and folders on demand using its built-in templates, with no prerequisite tools or configurations needed.