Build and verify Google Forms with requirement traceability, branching, validation, publish controls, safe updates, and an operational handoff.
A Google Form can look finished while still collecting the wrong data. A required question may have no approved reason to exist. One branch can skip a critical section. A timed-out update can be retried into duplicate questions. A published form can be mistaken for a working notification or filing workflow.
Google Forms Builder starts with the respondent, business purpose, source requirements, privacy boundary, and separate authority to read, design, create, update, publish, collect responses, share, connect another service, notify, or delete. It keeps approved, reported, inferred, missing, conflicting, and unsupported requirements distinct.
The workflow turns requirements into a question matrix, respondent path, validation rules, branch map, and exact mutation plan. It inspects the current Google Workspace CLI schemas before composing commands, preserves stable form and item identity, separates empty-form creation from batch updates and publication, and defines independent read-back before a change can be called verified.
Ambiguous writes stay unknown until the exact form is read back. The package distinguishes an exact match, no effect, partial effect, conflict, multiple matches, and unavailable evidence, so a timeout does not become a blind retry. It also keeps Forms configuration separate from Sheets, Drive, Gmail, Apps Script, notification, and HR-system claims that need their own authority and proof.
The included delivery contract supports a machine-checkable handoff covering identity, requirements, question records, operations, verification gates, authority, and conservative verdict states. The package cannot authenticate a Google account, approve privacy or legal language, prove a person submitted the form, or verify an external automation without the relevant access and evidence.
Version 1.0.0 was evaluated on 27 July 2026 through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. Across three cases, the candidate scored 95.83, compared with 84.17 for the same agent without the skill and 87.5 for the exact free upstream. It passed every case and led the comparison arms by 11.67 and 8.33 points overall. The cases covered branching intake design, ambiguous live-update recovery, and a blocked compliance-quiz launch. This evaluation measures the supplied cases; it does not prove that a real form or downstream workflow was delivered.
The reviewed package SHA-256 is 7f2292b47513d81e5832c926cb07f210d057a71facdc58f5bc796c7b93d39b6b. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
Design a partner application for agencies. Regulated-client applicants need an extra sector section. Sales also requested passport scans and employee emails, but no decision need or approved consent exists. Draft only.
Output
A requirement matrix, accessible respondent path, exact question and validation plan, complete branch map, blocked sensitive fields, API capability checks, read-back plan, and a design-ready handoff without claiming a live form.
Input
Form 1FAIpQLSeExact42 may have received one optional 1-10 question and new confirmation copy. The batch command timed out, a screenshot is incomplete, and approval covers no other change.
Provide the form purpose, owner, respondents, requirements and source authority, existing form ID when applicable, question and branching needs, privacy and retention rules, current state, and separate permission to read, create, update, publish, collect, share, notify, or connect downstream tools. Ask for a form design, safe gws command plan, live-update reconciliation, publish review, response-collection review, or operational handoff.
Purpose, owner, respondent groups, language, deadline, success criteria, and whether the task is inspect, design, create, update, publish, collect, close, or audit.
Approved questions and behavior, branching, validation, confirmation copy, quiz rules when applicable, privacy classification, consent source, retention, accessibility, and response-access owners.
Stable Google Form ID for an existing form, current snapshot or revision, observed settings and items, prior operation evidence, and known downstream integrations.
Separate permission to read, design, create, update, publish, collect responses, share, connect other services, notify respondents, close, or delete.
SKILL.md; Google Forms delivery contract; Codex interface metadata
No reviews yet.
Output
An unknown-state record, exact forms.get comparison, outcome branches for exact match, no effect, partial effect, conflict, or unavailable evidence, and a bounded retry or repair rule that preserves the original approval.
Input
Ten questions and answer keys are approved, but one source says the pass mark is 80% and the signed standard says 90%. Identity, retention, retakes, access, and HR recording are unspecified. Publish today.
Output
A blocked quiz specification that preserves the scoring conflict, maps approved content, lists owner decisions, checks current API support, separates every authority, rejects the HR claim, and names the smallest gates before creation or publication.
Creator
Vvorlin60
