Skip to content

Latest commit

 

History

History

README.md

Template Library

This is the product layer of the Agent Workflow Blueprint: 100 copy-ready assets for controlling coding-agent work with evidence, specialist review, and honest final status.

What is included

  • 40 scenario-specific prompts for execution, review, UI, accessibility, testing, security, documentation, and release control.
  • 30 executable skills for repeatable agent workflows.
  • 30 enforceable contracts for acceptance, rejection, and evidence gates.

Every asset contains at least 20 numbered enforcement points and uses the same final status vocabulary: verified, partially verified, not verified, blocked.

Use the system this way

  1. Choose the smallest prompt that matches the task.
  2. Attach the matching skill when the work needs a repeatable procedure.
  3. Attach the matching contract when the result needs acceptance or rejection language.
  4. Run repository verification from requirements.toml where applicable.
  5. Do not claim more than the evidence proves.

Fast paths

Human-readable catalogue

Open CATALOGUE.md for all 100 assets grouped by type and category.

Machine-readable catalogue

Open assets.json for site integration and automation.

Usage rule

Do not paste these assets blindly. Select the smallest asset that matches the failure mode, then combine it with AGENTS.md, docs/engineering/workflow.md, and the relevant engineering contract.

Research-backed upgrade layer

This library now includes a stronger scientific-control layer:

The product does not rely on prompt length alone. It relies on observable controls: decomposition, branch comparison, environment observation, independent verification, correction loops, traceable acceptance, and failure disclosure.

Research-backed architecture layer

This library now includes a dedicated scientific-DNA layer:

  • SCIENTIFIC-DNA.md — maps CoT-safe public reasoning, Tree-of-Thoughts-style branching, ReAct loops, least-to-most decomposition, self-consistency, self-refinement, process supervision, constitutional/contract critique, and traceability to repository behaviour.
  • PROMPT-ARCHITECTURE.md — defines the nine-layer structure used by high-risk prompts.
  • TRACEABILITY-MATRIX.md — provides the requirement-to-evidence matrix used by contracts and release gates.
  • SYSTEM-2-PROMPTING-GUIDE.md — explains how to use “System 2” as a deliberate-work metaphor without overclaiming human-like cognition.

The key rule is: ask agents for a public decision record and evidence trail, not hidden chain-of-thought.