bridge_skill

This skill translates business requirements into technical specs, detects scope creep, and documents decisions to align stakeholders and prevent

Shell

8

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill simota/agent-skills --skill bridge

SKILL.md11.7 KB

Overview

This skill translates and mediates between business stakeholders and engineers to prevent costly misunderstandings. It clarifies ambiguous requirements, detects scope creep early, explains technical trade-offs in business terms, and maintains a decision log to preserve context and rationale.

How this skill works

Bridge inspects incoming requirements, stakeholder statements, and technical responses to surface hidden assumptions and ambiguous language. It produces concise clarification prompts, flags scope changes and feasibility issues, and provides trade-off options framed as business impacts. It coordinates handoffs to specification and implementation agents while logging decisions and open questions.

When to use it

At project kickoff to validate and make requirements concrete
When business requests change during implementation
Before committing to deadlines or high-cost technical approaches
When stakeholder expectations diverge or priorities conflict
When engineers refuse work without business context

Best practices

Ask targeted, specific clarification questions rather than broad ones
Document assumptions and required approvals immediately
Convert technical constraints into measurable business impacts (cost, time, risk)
Provide 2–3 actionable trade-off options, with pros/cons and recommended next steps
Create short decision-log entries after every alignment session

Example use cases

PM submits a one-line feature request; Bridge expands into precise acceptance criteria and hidden dependencies
Engineering flags a feasibility concern; Bridge translates impact to the business and proposes alternatives
Scope starts expanding mid-sprint; Bridge issues a scope-change alert and outlines required approvals and impact
Stakeholders disagree on quality levels; Bridge facilitates a must/should/nice-to-have prioritization and documents consensus
Product team receives customer feedback that implies unrealistic expectations; Bridge surfaces assumptions and recommends validation steps

FAQ

No. Bridge clarifies requirements, surfaces assumptions, and hands off to spec and implementation owners (Scribe, Builder). It coordinates but does not produce final code or full PRDs.

When should Bridge escalate a conflict?

Bridge asks for alignment first. It escalates only when priorities or scope cannot be resolved at the stakeholder level or when changes would breach agreed approvals or timelines.

How does Bridge detect scope creep?

Bridge monitors deviations from signed scope, tracks conversational signals (e.g., “while we’re at it”), compares current work to original acceptance criteria, and issues alerts with impact summaries.

What outputs does Bridge create?

Clarification prompts, alignment summaries, scope-change alerts, trade-off options, and concise decision-log entries for handoff and audit.