meta-prompt

Coordinate pre-build and active-build checks to prevent Winston regressions.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/paulmalmquist/Consulting_app --skill meta-prompt-paulmalmquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-prompt
Source: https://github.com/paulmalmquist/Consulting_app/tree/main/skills/meta-prompt
Command: npx skills add https://github.com/paulmalmquist/Consulting_app --skill meta-prompt-paulmalmquist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive pre-build and active-build harness that captures every concern Winston/Novendor developers worry about when implementing features, fixing bugs, or extending the platform. Produces a concern-aware build plan AND stays active as a guardrail harness during implementation. Use this skill before starting ANY non-trivial Winston work — feature builds, bug fixes, new surfaces, schema changes, prompt edits, write-tool additions, dashboard work, credit decisioning changes, PDS phases, or performance optimization. Also use when someone says "build this", "implement this", "add this feature", "fix this", or any task that touches multiple surfaces. If you're about to start writing code in the Winston repo and haven't loaded this skill, stop and load it first. This is the "did I think of everything?" checklist that prevents the regressions we've actually had.

Core Features & Use Cases

The skill operates in two phases: Plan (before you write code) and Harness (while you write code). It generates a concern-aware build plan and remains active as a guardrail during implementation to catch regressions across surfaces.

Quick Start

Load this skill before starting Winston work to ensure all concerns are captured and guardrails stay active during implementation.

Frequently Asked Questions about meta-prompt

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

FAQPage Schema
How do I prevent regressions when implementing features across multiple surfaces?

A pre-build harness prevents regressions by capturing concerns before you start coding. It generates a concern-aware build plan and remains active as a guardrail during implementation to catch issues across multiple platform surfaces.

What is a concern-aware build plan and when do I need it for schema changes?

A concern-aware build plan is a comprehensive checklist capturing every regression risk before coding. You need it for schema changes, bug fixes, prompt edits, or any non-trivial platform task touching multiple surfaces.

How do I set up a build harness guardrail during active implementation?

Set up a build harness guardrail by loading a two-phase workflow before coding. It operates in a Plan phase to map concerns and a Harness phase to actively check for regressions as you write code.

Does the build harness require YAML frontmatter for SKILL.md files?

Yes, the build harness requires YAML frontmatter in SKILL.md files. The frontmatter must include name and description fields, and the harness validates this presence before allowing feature work to proceed.

Can I use pre-build checks for bug fixes and performance optimization tasks?

Yes, you can use pre-build checks for bug fixes and performance optimization. The harness applies to any non-trivial work including new surfaces, dashboard work, credit decisioning changes, and PDS phases.

What are the limitations of using a build harness for prompt edits?

The build harness for prompt edits focuses on ensuring YAML frontmatter presence and system-prompt coherence. It does not replace manual review of conversational logic but actively guards against regressions across affected surfaces.