skills.rest
MJ-AgentLab
MJ-AgentLabOFFICIAL
Explore all skills by this author →
GitHub

plan

Analyze documentation requirements and generate implementation plans for MJ System topics.

Updated Mar 16, 2026
Search Tags:#planning#documentation#specification#gap analysis#runbook#mj-doc
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill plan-mj-agentlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/MJ-AgentLab/mj-agentlab-marketplace/tree/main/plugins/mj-doc/skills/mj-doc-plan
Command: npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill plan-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill determines precisely what documentation is required for a given topic, service, or infrastructure area, identifying gaps and creating a clear plan for their creation.

Core Features & Use Cases

  • Documentation Gap Analysis: Assesses existing documentation against framework requirements to find missing pieces.
  • Document Type Determination: Uses a decision tree to identify the correct type of document needed (e.g., SPEC, RUNBOOK, GUIDE, ADR).
  • Implementation Planning: Generates a structured plan outlining tasks, dependencies, and verification steps.
  • Use Case: Before starting a new microservice, use this skill to understand what SPEC, RUNBOOKs, and potentially ADRs need to be written.

Quick Start

Use the plan skill to evaluate documentation needs for the new user authentication service.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I perform a documentation gap analysis for a new microservice?▼

Documentation gap analysis evaluates existing materials against Framework v4 requirements to identify missing pieces. It assesses code scope to determine necessary document types, ensuring complete coverage for your service infrastructure.

What document types do I need to write for my infrastructure topic?▼

Document type determination uses a decision tree to identify the correct format required, such as SPEC, RUNBOOK, GUIDE, or ADR. This ensures you create the precise documentation needed for your specific service.

How do I generate an implementation plan for writing missing documentation?▼

Implementation planning generates a structured plan outlining tasks, dependencies, and verification steps for documentation creation. This provides a clear roadmap to build out required specifications and runbooks.

When do I need documentation planning for my MJ System services?▼

Documentation planning is needed before starting a new microservice or infrastructure area to understand what specifications and runbooks must be written. It triggers on phrases related to needs assessment and gap analysis.

Does this documentation planning approach work with Framework v4?▼

Yes, this approach evaluates documentation requirements specifically against Framework v4. It analyzes code scope within this framework to identify necessary document types and assess existing gaps accurately.

Related Skills

Explore More Software Engineering Skills→
toongritoongri
25

performance-optimizer

Analyze and optimize system performance through structured measurement and iterative improvement cycles.

Community
Advanced
MJ-AgentLabMJ-AgentLab

author

Generate Framework v4-compliant MJ System documents from code analysis.

Official
Advanced
Knuckles-TeamKnuckles-Team

spec-to-backlog

Convert Confluence specifications into Jira Epics and linked tickets.

Official
Intermediate
michaelsvanbeekmichaelsvanbeek
1

dependency-management

Evaluate Python or JavaScript dependencies and produce a formal decision report.

Community
Advanced