planning

Comprehensive Planning & Architecture skill for the Software Development Life Cycle. Guides agents through architecture design, technology decisions, task decomposition, milestone planning, environment infrastructure, risk mitigation, and CI/CD pipeline design. Produces structured artifacts: technical specs, Architecture Decision Records (ADRs), roadmaps, task breakdowns, risk registers, and environment plans. Trigger phrases: "plan architecture", "write technical spec", "create ADR", "decompose tasks", "plan milestones", "architecture decision", "plan roadmap", "plan environment", "risk assessment", "CI/CD pipeline design", "technical planning", "sprint planning".

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "planning" with this command: npx skills add azmankudus/skillsmp-azmankudus-azmankudus-planning

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

Coding

knowledge

Comprehensive Knowledge Management & Documentation skill for the SDLC. Governs all documentation artifacts: scaffolding, product specifications via interview mode, versioned roadmaps, developer onboarding guides, ADR lifecycle management, documentation health scoring, operational runbooks, and support clusters (FAQ, triage, SLA, post-mortem). Enforces documentation linting rules and badge standards across the entire project. Follows docs-as-code principles where every artifact is version-controlled, linted, and reviewed like production code. Trigger phrases: "write documentation", "onboard developer", "create ADR", "generate docs", "knowledge base", "FAQ", "runbook", "changelog", "documentation scaffold", "product specification", "roadmap", "doc health", "documentation standards", "support docs", "triage guide", "SLA template", "post-mortem", "doc linting", "validate docs", "developer guide". Tech stack assumptions: Frontend — Bun 1.2+ + TypeScript 5.8 (strict) + SolidJS 1.9+ + SolidStart (SSG)

Repository SourceNeeds Review

-0azmankudus

Automation

build-release

Build & Release skill for the "Build & Release" phase of the SDLC. Provides containerization, CI/CD pipeline generation, version management, release automation, and deployment strategies for the full-stack architecture: - **Frontend**: SolidJS SSG → Bun build → nginx:stable-alpine container - **Backend**: Micronaut → Shadow JAR → Liberica CRaC container Trigger phrases: - "build container" - "create dockerfile" - "set up CI/CD" - "deploy" - "release version" - "build pipeline" - "containerize"

Repository SourceNeeds Review

-0azmankudus

Security

design

Comprehensive design-phase skill for the SDLC "Design" stage. Produces concrete, implementation-ready artifacts: UI/UX layouts with TailwindCSS v4 (@theme directive, CSS-first configuration), SolidJS 1.9 component architecture, data models with Flyway migration strategies, OpenAPI 3.1 API contracts, and security designs covering JWT/OAuth2, RBAC/ABAC, CORS, and input validation (Zod/Valibot on the frontend, Micronaut validation on the backend). Trigger phrases: "design UI", "design API", "data model", "component architecture", "design system", "API contract", "security design", "ER diagram", "database schema", "REST API design", "component tree", "state architecture", "layout design", "pagination strategy", "error handling design". Tech stack assumptions: Frontend — Bun + TypeScript 5.8 (strict) + SolidJS 1.9 + SolidStart (SSG) + TailwindCSS 4.1 (CSS-first @theme) + Iconify-Solid Backend — Java 21 (records, sealed interfaces, virtual threads, pattern matching) + Micronaut 4.7

Repository SourceNeeds Review

-0azmankudus

Web3

discovery

Discovery & Requirements Gathering phase of the SDLC. Systematically elicit, analyze, and document product requirements before design or implementation begins. TRIGGER when: user mentions "gather requirements", "write PRD", "create user stories", "feasibility check", "stakeholder interview", "discovery phase", "requirements elicitation", "define scope", "product requirements", "need a spec", "what should we build", "project kickoff", "business requirements", "functional requirements", "non-functional requirements", "acceptance criteria", "domain model", "competitive analysis", "MoSCoW", "5W1H", "user story mapping", "define MVP", "scope the project", or starts a new project with ambiguous or incomplete requirements.

Repository SourceNeeds Review

-0azmankudus