skills.rest
Keiji-Miyake
Keiji-MiyakeCOMMUNITY
Explore all skills by this author →
𝕏@KE_JI00GitHub

dev-support

Organize development session context with SPEC, DESIGN, TEST_PLAN, ROADMAP, and CONTEXT documents.

Updated Jan 19, 2026
Search Tags:#documentation#context#project-management#context-management#interruption#two-tier-docs
One-click install
npx skills add https://github.com/Keiji-Miyake/agent-skills --skill dev-support
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-support
Source: https://github.com/Keiji-Miyake/agent-skills/tree/main/skills/dev-support
Command: npx skills add https://github.com/Keiji-Miyake/agent-skills --skill dev-support

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams maintain momentum by organizing and preserving work context across interrupted development sessions, reducing cognitive load when resuming.

Core Features & Use Cases

  • Two-tier documentation structure: project-level docs and feature-level docs to track progress and decisions.
  • Context preservation: CONTEXT.md and ROADMAP to capture last state, next actions, and milestones.
  • Documentation-driven development: SPEC, DESIGN, TEST_PLAN, ROADMAP, and CONTEXT guide the workflow across any tech stack.

Quick Start

Create a new feature under docs/dev/your-feature and generate SPEC.md, DESIGN.md, TEST_PLAN.md, ROADMAP.md, CONTEXT.md, then start the first session.

Frequently Asked Questions about dev-support

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

FAQPage Schema
How do I preserve development context across interrupted sessions?▼

To preserve development context across interrupted sessions, maintain a CONTEXT.md file capturing the last state and next actions, reducing cognitive load when resuming work.

What is a two-tier documentation workflow for project management?▼

A two-tier documentation workflow separates project-level docs from feature-level docs, organizing SPEC, DESIGN, TEST_PLAN, ROADMAP, and CONTEXT files to track decisions and progress across any tech stack.

How do I start documentation-driven development for a new feature?▼

To start documentation-driven development, create a new feature directory under docs/dev/ and generate SPEC.md, DESIGN.md, TEST_PLAN.md, ROADMAP.md, and CONTEXT.md before beginning your first session.

Can I use this context management approach with any tech stack?▼

Yes, this context management approach works with any tech stack because it relies on standard markdown files for documentation rather than framework-specific configurations or platform-specific dependencies.

When do I need context management for short development sessions?▼

You need context management for short development sessions when frequent interruptions cause you to lose track of milestones and next actions, requiring structured ROADMAP and CONTEXT files to maintain momentum.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:init-repo

Initialize a GSD repository structure with Git and planning documents.

Community
Intermediate
vh2224vh2224
3

forge-add-slice

Add a slice to a milestone and generate S##-PLAN.md and T##-PLAN.md files.

Community
Advanced
usk6666usk6666
11

project

Synchronize roadmap documents with development issues in Linear.

Community
Advanced
shep-aishep-ai
241

shep-kit:new-feature

Generate a feature specification directory with YAML templates and Markdown artifacts.

Official
Intermediate