domains / families / software-engineering / blueprint

blueprint

combined

Use when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground. Turn a one-line objective into a step-by-step construction plan any coding agent can execute cold. Each step has a self-contained context brief — a fresh agent in a new session can pick up any step without reading prior steps.

When to use

• Use when the task requires multiple PRs or sessions
• Use when multiple agents or team members need to share execution
• Use when you want adversarial review of the plan before execution
• Use when parallel step detection and dependency graphs matter

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
• A pinned revision is reproducible, not automatically trustworthy; its contents still require review.

Skill page

Conflict

The two copies use the same name for completely different tasks. The WordPress copy is a reference for authoring and validating WordPress Playground Blueprint JSON files. The sickn33 copy is a meta-skill for generating step-by-step construction plans for coding agents. They do not overlap in procedure, and crowning one would hide the other's distinct purpose.