Techtide human approval gate designer

TechTide Human Approval Gate Designer

Design explicit human approval gates for agent workflows that can mutate production, spend money, contact external recipients, delete data, or change security posture.

Source Pattern

This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load references/source-patterns.md when you need the source anchors and extraction rationale. Load references/adapter-map.md when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.

Workflow

1. Identify the risky action, target system, actor, blast radius, reversibility, and evidence required.
2. Define the exact approval phrase or UI checkpoint needed before execution.
3. Require dry-run output, rollback plan, and target confirmation for live changes.
4. Log approval metadata without storing secrets or sensitive payloads.
5. Block automation if approval is stale, ambiguous, or mismatched to the target.

Output Contract

Return a concise brief with these fields:

• approval contract
• dry-run evidence
• rollback plan
• audit fields
• verification performed or still required
• security and privacy notes

Guardrails

• Extract reusable methods, not private local content.
• Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.
• Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.
• Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.
• Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.

Harness Policy

• Use this as a native SKILL.md for Claude Code, Codex, Gemini, and Copilot-compatible exports.
• For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.
• For Kiro, create steering only when the workflow can be made short and inclusion-scoped.
• For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.