skills.rest
loagma
loagmaCOMMUNITY
Explore all skills by this author →
GitHub

planning-guidelines

Define production-ready planning guidelines for scalable software projects.

Updated Feb 7, 2026
Search Tags:#planning#performance#scalability#governance#reliability#guidelines#best-practices
One-click install
npx skills add https://github.com/loagma/LoagmaPMS --skill planning-guidelines-loagma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-guidelines
Source: https://github.com/loagma/LoagmaPMS/tree/main/.claude/skills/planning-guidelines
Command: npx skills add https://github.com/loagma/LoagmaPMS --skill planning-guidelines-loagma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines for creating comprehensive, production-ready plans that account for extreme scalability, performance, reliability, and best practices. Apply when planning features, creating plan documents, or breaking down complex tasks.

Core Features & Use Cases

  • Structured planning templates and checklists to ensure production polish.
  • Research-driven guidelines that incorporate industry best practices and guardrails.
  • Use Case: Develop a plan that anticipates scale, reliability, and performance constraints.

Quick Start

Apply these guidelines to your next feature plan to ensure production readiness and measurable quality.

Frequently Asked Questions about planning-guidelines

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

FAQPage Schema
What should production-ready software planning guidelines include for extreme scalability?▼

Planning guidelines for scalable software establish research-driven guardrails and structured templates that incorporate industry best practices for architecture reviews, feature planning, and roadmap documentation across technology stacks.

How do I create a scalable architecture review plan?▼

Apply structured planning guidelines and checklists to your architecture review to anticipate scale, reliability, and performance constraints while ensuring production readiness and measurable quality across your technology stack.

Can these planning guidelines be used for feature planning across different technology stacks?▼

Yes, these planning guidelines apply to feature planning, architecture reviews, and roadmap documentation across various technology stacks, helping define production-ready plans without stack-specific dependencies.

What is the best way to ensure production readiness in a software roadmap document?▼

The best way to ensure production readiness is to apply research-driven guidelines with structured checklists that enforce industry best practices and guardrails for scalability, performance, reliability, logging, and governance directly into your roadmap documentation.

Do I need specific frameworks to implement these scalability and reliability guidelines?▼

No, you do not need specific frameworks. The guidelines operate without external dependencies and are applicable across technology stacks, allowing you to define scalable and reliable software plans independently.

When should I not use structured planning guidelines for software projects?▼

Avoid using structured planning guidelines for simple prototypes or trivial tasks that do not require production polish, extreme scalability, reliability, performance logging, or strict governance practices.

Related Skills

Explore More Product & Management Skills→
ydnikolaevydnikolaev
8

idea-interview

Extract project information through structured stakeholder interviews into a discovery brief.

Community
Advanced
clouseryanclouseryan

architect-agent

Plan and validate software architecture decisions with ADR generation and implementation blueprints.

Community
Advanced
saeed-vayghansaeed-vayghan
30

devops-engineer

Automate infrastructure, CI/CD pipelines, and monitoring with Terraform, Ansible, Docker, and Kubernetes.

Community
Advanced
JeremyDev87JeremyDev87
31

deployment-checklist

Enforce pre-deploy validation, environment checks, and rollback planning for deployments.

Community
Advanced