dev.plan

Transform a clarified spec into plan.md, research.md, and related design artifacts.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev.plan
Source: https://github.com/Obsidian-Owl/agentlint/tree/main/.claude/skills/dev.plan
Command: npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This skill guides teams through a disciplined planning workflow to turn a feature specification into a concrete design plan, research artifacts, and related documentation.

Core Features & Use Cases

  • Environment setup and planning: Initialize plan templates, extract prerequisites, and define technical context.
  • Artifact generation: Create plan.md, research.md, data-model.md, quickstart.md, and contracts/ to enable phase-based development.
  • Guided execution: Step-through phases (Setup, Research, Design) with gate checks against constitution.

Quick Start

Use /dev.plan to initialize planning artifacts for a feature branch, then fill in plan.md and run checks to ensure compliance.

Frequently Asked Questions about dev.plan

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

FAQPage Schema
How do I generate design artifacts for a feature specification?

The planning workflow transforms a clarified feature specification into actionable design artifacts like plan.md, research.md, data-model.md, quickstart.md, and contracts/. It initializes plan templates, extracts prerequisites, and validates compliance with a constitution.

What are feature spec gate checks and how do they work?

Feature spec gate checks validate planning compliance against a defined constitution during phase transitions. They ensure artifacts generated during Setup, Research, and Design phases align with technical requirements before advancing to the next development stage.

Do I need jq installed to create plan.md and research.md templates?

Yes, jq is required as a dependency to create plan.md and research.md templates. The planning scripts rely on jq to process JSON configurations, extract prerequisites, and define the technical context for feature branch setup.

What's the best way to structure data-model.md and contracts for a new feature branch?

The best way to structure data-model.md and contracts is through a disciplined planning workflow that steps through Setup, Research, and Design phases. This generates aligned artifacts directly on the feature branch while enforcing constitution compliance.

Can I use these planning templates without a defined constitution file?

No, a constitution file is required. The planning workflow explicitly validates gate checks against a constitution to ensure generated artifacts like plan.md and data-model.md comply with predefined technical constraints and project standards.