core-dev

Route development tasks to language-specific skills using plan and chronicle files.

10|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/reidemeister94/development-skills --skill core-dev-reidemeister94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-dev
Source: https://github.com/reidemeister94/development-skills/tree/main/skills/core-dev
Command: npx skills add https://github.com/reidemeister94/development-skills --skill core-dev-reidemeister94

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate development tasks by routing them through a plan-driven workflow, preserving rationale and decisions on disk for context.

Core Features & Use Cases

  • Reads and resumes progress from plan files under docs/plans/ to ensure continuity across sessions.
  • Captures the WHY in chronicles under docs/chronicles/ and automatically routes tasks to the appropriate language-specific skill (frontend-dev, python-dev, typescript-dev, java-dev, swift-dev).
  • Supports specialized routes for debugging and test creation, and prompts for brainstorming when needed.
  • Activates based on task context, then loads the suitable sub-skill to implement the code with plan-guided steps.

Quick Start

Ingest a new development task and let the router resume from the existing plan or start brainstorming and routing to the right sub-skill.

Frequently Asked Questions about core-dev

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

FAQPage Schema
How do I orchestrate development tasks across multiple programming languages?

Orchestrate development tasks by using a smart workflow that dynamically routes work to language-specific skills like frontend-dev, python-dev, or java-dev. It preserves rationale and ensures continuity across coding sessions.

How do I preserve architecture decisions and rationale across coding sessions?

Preserve architecture decisions by capturing the WHY in chronicle files under docs/chronicles/ and tracking progress in plan files under docs/plans/. This on-disk documentation maintains project context and guides development steps.

Can I resume a refactoring or bug fix workflow from a previous session?

Yes, you can resume a refactoring or bug fix workflow by reading existing plan files under docs/plans/. The workflow reads your saved progress to ensure continuity and routes the remaining coding tasks to the appropriate specialized skill.

Does this workflow support routing to specialized debugging and test creation skills?

Yes, the workflow supports specialized routes for debugging and test creation alongside language-specific routing. It activates these routes based on task context to implement code with plan-guided steps.

What is the best way to manage brainstorming and architecture decisions in a coding project?

Manage brainstorming and architecture decisions by ingesting the development task into the orchestration workflow. It prompts for brainstorming when needed and documents decisions in chronicles under docs/chronicles/ before routing to implementation.

Do I need specific directory structures to run the development workflow?

Yes, the development workflow requires plan files under docs/plans/ and chronicles under docs/chronicles/ to function. These directories are necessary to store progress and capture rationale for routing tasks.