Skip to content
production / main000%
All tools
PROMPT-01SPEC BUILDEROSS-READY / LOCAL-FIRST

Prompt Specification Architect

It does not generate magic words for a specific model. It first turns the task into a contract, then produces an explicit execution prompt suitable for a team, research agent or coding agent.

PROMPT-01 / WORKBENCH 3.0

Primary output is portable as PDF, Markdown and machine-readable JSON.

Advanced contract fields
PROMPT CONTRACT · INCOMPLETE
0/100
# Prompt Specification

## Work type
Coding / implementation

## Role
Assume the specialist role appropriate to the task.

## Objective
[Objective required]

## Task
[Task required]

## Inputs / available context
Use only inputs explicitly provided in this prompt or through connected tools.

## Constraints
- Do not guess missing facts; mark assumptions explicitly.

## Output contract
[Specify format, fields, length and delivery shape]

## Acceptance criteria
- The result must directly satisfy the objective without violating stated constraints.

## Uncertainty and failure behavior
If critical information is missing, state it; do not fabricate information that cannot be reliably derived.

## Examples / references
No example supplied. Do not invent extra requirements from the absence of examples.

## Execution protocol
1. Separate the objective, inputs and constraints before acting.
2. If context conflicts with the instruction contract, preserve the instruction hierarchy and surface the conflict.
3. Do not make critical assumptions silently.
4. Validate the result against the acceptance criteria before delivery.
5. Do not add unrelated explanation, scope or goals beyond the requested output.
Promptfoo eval taslağı
# Promptfoo eval scaffold generated by ahmetcanal.com
# Replace YOUR_PROVIDER/YOUR_MODEL before running.
description: "Prompt Specification Architect"

prompts:
  - |
      # Prompt Specification
      
      ## Work type
      Coding / implementation
      
      ## Role
      Assume the specialist role appropriate to the task.
      
      ## Objective
      [Objective required]
      
      ## Task
      [Task required]
      
      ## Inputs / available context
      Use only inputs explicitly provided in this prompt or through connected tools.
      
      ## Constraints
      - Do not guess missing facts; mark assumptions explicitly.
      
      ## Output contract
      [Specify format, fields, length and delivery shape]
      
      ## Acceptance criteria
      - The result must directly satisfy the objective without violating stated constraints.
      
      ## Uncertainty and failure behavior
      If critical information is missing, state it; do not fabricate information that cannot be reliably derived.
      
      ## Examples / references
      No example supplied. Do not invent extra requirements from the absence of examples.
      
      ## Execution protocol
      1. Separate the objective, inputs and constraints before acting.
      2. If context conflicts with the instruction contract, preserve the instruction hierarchy and surface the conflict.
      3. Do not make critical assumptions silently.
      4. Validate the result against the acceptance criteria before delivery.
      5. Do not add unrelated explanation, scope or goals beyond the requested output.

providers:
  - id: YOUR_PROVIDER:YOUR_MODEL

tests:
  - description: "Basic output check"
    assert:
      - type: javascript
        value: output.trim().length > 0

# Run locally with Promptfoo after choosing a provider/model.
Taşınabilir prompt payload
{
  "name": "prompt-specification-architect",
  "type": "text",
  "prompt": "# Prompt Specification\n\n## Work type\nCoding / implementation\n\n## Role\nAssume the specialist role appropriate to the task.\n\n## Objective\n[Objective required]\n\n## Task\n[Task required]\n\n## Inputs / available context\nUse only inputs explicitly provided in this prompt or through connected tools.\n\n## Constraints\n- Do not guess missing facts; mark assumptions explicitly.\n\n## Output contract\n[Specify format, fields, length and delivery shape]\n\n## Acceptance criteria\n- The result must directly satisfy the objective without violating stated constraints.\n\n## Uncertainty and failure behavior\nIf critical information is missing, state it; do not fabricate information that cannot be reliably derived.\n\n## Examples / references\nNo example supplied. Do not invent extra requirements from the absence of examples.\n\n## Execution protocol\n1. Separate the objective, inputs and constraints before acting.\n2. If context conflicts with the instruction contract, preserve the instruction hierarchy and surface the conflict.\n3. Do not make critical assumptions silently.\n4. Validate the result against the acceptance criteria before delivery.\n5. Do not add unrelated explanation, scope or goals beyond the requested output.\n",
  "tags": [
    "ahmetcanal",
    "prompt-tools"
  ],
  "metadata": {
    "source": "ahmetcanal.com",
    "useCase": "coding",
    "coverage": 0
  }
}

AVAILABLE FOR PROJECTS · PRODUCT & SYSTEMS ARCHITECT · TAKEOVER / STABILIZE / OPERATE · WEB · ANDROID · WINDOWS · AHMET CANAL

Contact

Has your product grown faster than its system?

Send the current situation, your biggest blocker and the outcome you want. We will clarify scope together.

Availability

Open to new consulting and project-based work.

GROWTH / SIGNAL LOOP

Move from reading to a decision.

Booking, feedback and system notes in one low-friction exit.

CNV-01

Technical call

If there is a fit, move directly to a 20-minute call.

CNV-02

Decision blocker

Tell me what is still missing with one signal.