Pattern: Sequential Pipeline | Team size: 5 agents
This team moves the concept from user insight to interaction design, implementation, agreement generation, and launch readiness in a clear sequence. A pipeline fits because the tool has a natural build flow: understand parent-child needs, design the experience, create the contract logic, then validate that the final printable agreement feels trustworthy and empowering.
Interactive Screen-Time Contract Builder — A highly interactive, child-friendly web tool where parents and kids select visual icons representing daily tasks (e.g., brush teeth, read a book, clean toys) that must be completed to unlock screen time. It generates a personalized, downloadable, and printable "Family Screen Time Agreement." — It acts as the final step in establishing healthy screen habits, transitioning the parent from "worried" to "in control."
Create an agent team to design the “Interactive Screen-Time Contract Builder,” a highly interactive, child-friendly web tool where parents and kids select visual icons representing daily tasks that must be completed to unlock screen time. The tool must generate a personalized, downloadable, and printable “Family Screen Time Agreement.” It must act as the final step in establishing healthy screen habits, moving the parent emotionally from “worried” to “in control.” Use the team design below. Team name: Kid-Friendly Product Sprint Squad Pattern: Sequential Pipeline Operating model: Run the agents in order. Each agent must read all prior outputs before starting. Each agent must add handoff notes for the next agent, explicitly challenge at least 2 assumptions from prior work where applicable, and preserve decisions in a shared log. Create all deliverables as Markdown files in this directory: outputs/agent_teams_demo/interactive_screen_time_contract_builder/ Required files: 1. outputs/agent_teams_demo/interactive_screen_time_contract_builder/00_team_brief.md 2. outputs/agent_teams_demo/interactive_screen_time_contract_builder/01_family_needs_research.md 3. outputs/agent_teams_demo/interactive_screen_time_contract_builder/02_child_ux_flow_design.md 4. outputs/agent_teams_demo/interactive_screen_time_contract_builder/03_visual_task_icon_library.md 5. outputs/agent_teams_demo/interactive_screen_time_contract_builder/04_agreement_template_builder.md 6. outputs/agent_teams_demo/interactive_screen_time_contract_builder/05_qa_launch_readiness.md 7. outputs/agent_teams_demo/interactive_screen_time_contract_builder/06_synthesis_review.md 8. outputs/agent_teams_demo/interactive_screen_time_contract_builder/99_assumptions_decisions_log.md Global requirements: - Use clear, parent-friendly language. - Optimize for children ages 4–12, with notes for 4–6, 7–9, and 10–12 where relevant. - Treat the parent as anxious but motivated. The product must reduce guilt, conflict, ambiguity, and negotiation fatigue. - Treat the child as capable, visual, reward-motivated, and sensitive to feeling controlled. - Make the experience collaborative: parent and child build the agreement together. - Avoid shame-based language, punitive framing, dark patterns, or fear tactics. - Include accessibility considerations throughout: plain language, keyboard access, color contrast, screen reader labels, printable readability, and mobile use. - Do not create generic advice. Tie every recommendation to this specific product. - Include concrete examples for tasks, rewards, agreement wording, and edge cases. - Keep each file structured exactly as specified below. - If information is uncertain, state the assumption and add it to 99_assumptions_decisions_log.md. - End with a synthesis/review step that evaluates coherence across all agent outputs. First, create 00_team_brief.md. File: outputs/agent_teams_demo/interactive_screen_time_contract_builder/00_team_brief.md Length: 700–1,000 words. Use exactly these sections: # Team Brief ## Product Goal Describe the tool in 120–180 words. ## Target Users Define parent user, child user, and family context. ## Emotional Job To Be Done Explain the transformation from “worried” to “in control.” ## Core User Journey List 7–10 numbered journey steps from arrival to printed/downloaded agreement. ## Non-Negotiable Product Principles List 8–12 bullets. ## Agent Pipeline List all 5 agents, their responsibilities, dependencies, and outputs. ## Shared Collaboration Rules Include how agents hand off insights, challenge assumptions, and update the log. ## Initial Assumptions List 10–15 assumptions to validate or carry forward. Also create or initialize: File: outputs/agent_teams_demo/interactive_screen_time_contract_builder/99_assumptions_decisions_log.md Use exactly these sections: # Assumptions and Decisions Log ## Assumptions Create a table with columns: ID, Assumption, Source Agent, Confidence, Impact, Needs Validation? ## Decisions Create a table with columns: ID, Decision, Source Agent, Rationale, Downstream Impact ## Open Questions Create a table with columns: ID, Question, Owner Agent, Why It Matters, Suggested Resolution Then run Agent 1. Agent 1: Family Needs Researcher Mission: Identify parent anxieties, child motivation triggers, age-appropriate task categories, and the emotional moments the tool must support. Dependency: - This task must complete after 00_team_brief.md is written. - This task must complete before Child UX Flow Designer, Visual Task Icon Curator, and Agreement Template Builder begin. Inputs to read: - outputs/agent_teams_demo/interactive_screen_time_contract_builder/00_team_brief.md - outputs/agent_teams_demo/interactive_screen_time_contract_builder/99_assumptions_decisions_log.md Output file: outputs/agent_teams_demo/interactive_screen_time_contract_builder/01_family_needs_research.md Length: 1,200–1,600 words. Use exactly these sections: # Family Needs Research ## Research Summary Write 150–220 words summarizing the parent-child problem. ## Parent Anxiety Map Create a table with columns: Anxiety, What Triggers It, Product Response, Agreement Implication. Include at least 8 anxieties. ## Child Motivation Map Create a table with columns: Motivation Trigger, Age Range, UX Implication, Icon/Task Implication. Include at least 8 triggers. ## Age-Appropriate Task Categories Create subsections for ages 4–6, 7–9, and 10–12. For each, list 8–12 tasks and explain why they fit. ## Family Conversation Moments Identify at least 6 moments where the product must guide parent-child dialogue. Include suggested microcopy for each. ## Healthy Screen Habit Guardrails List 10 practical guardrails the agreement should support, such as no screens before school tasks, bedtime cutoff, or homework first. ## Risks and Sensitivities List at least 8 risks, including power struggles, neurodiversity considerations, literacy differences, sibling fairness, and inconsistent enforcement. ## Assumptions Challenged Challenge at least 2 assumptions from 00_team_brief.md. State whether to keep, revise, or validate each. ## Handoff Notes for Child UX Flow Designer Provide 8–12 specific design implications. ## Handoff Notes for Visual Task Icon Curator Provide 8–12 task/icon implications. ## Handoff Notes for Agreement Template Builder Provide 8–12 agreement content implications. Update 99_assumptions_decisions_log.md: - Add at least 5 assumptions. - Add at least 3 decisions. - Add at least 3 open questions. Then run Agent 2. Agent 2: Child UX Flow Designer Mission: Design the step-by-step interactive experience so children can select icons easily while parents feel guided and in control. Dependency: - This task must complete after Family Needs Researcher finishes. - This task must complete before Visual Task Icon Curator finalizes icon organization. - This task must complete before Agreement Template Builder finalizes agreement logic. - QA and Launch Readiness Analyst cannot begin until this file exists. Inputs to read: - 00_team_brief.md - 01_family_needs_research.md - 99_assumptions_decisions_log.md Output file: outputs/agent_teams_demo/interactive_screen_time_contract_builder/02_child_ux_flow_design.md Length: 1,400–1,900 words. Use exactly these sections: # Child UX Flow Design ## UX Strategy Summary Write 150–220 words explaining the interaction approach. ## Primary Flow Create a numbered flow with 10–14 steps from landing page to downloadable agreement. For each step include: User Goal, Screen Elements, Parent Role, Child Role, Error/Edge State. ## Screen-by-Screen Wireframe Descriptions Describe at least 8 screens. For each include: - Screen Name - Purpose - Main Components - Suggested Microcopy - Accessibility Notes - Mobile Considerations ## Parent-Control and Child-Agency Balance Explain how the tool lets parents set boundaries while children feel ownership. Include 6–8 design patterns. ## Icon Selection Interaction Model Specify how children browse, select, deselect, categorize, and preview task icons. Include keyboard and touch behavior. ## Rules and Rewards Setup Define how users set screen-time amount, unlock conditions, bonus rewards, blackout times, and parent approval. ## Progress Feedback and Celebration Define animations, sounds, or visual feedback. Include low-stimulation alternatives. ## Edge Cases Address at least 10 edge cases, including non-readers, multiple children, divorced households, device sharing, incomplete tasks, and no printer. ## Assumptions Challenged Challenge at least 2 assumptions from earlier files. State whether to keep, revise, or validate each. ## Handoff Notes for Visual Task Icon Curator Provide 8–12 icon organization requirements. ## Handoff Notes for Agreement Template Builder Provide 8–12 data and template requirements. ## Handoff Notes for QA and Launch Readiness Analyst Provide 8–12 test focus areas. Update 99_assumptions_decisions_log.md: - Add at least 5 assumptions. - Add at least 4 decisions. - Add at least 3 open questions. Then run Agent 3. Agent 3: Visual Task Icon Curator Mission: Create and organize a child-friendly library of daily task icons such as brushing teeth, reading, cleaning toys, homework, outdoor play, kindness, chores, meals, and bedtime routines. Dependency: - This task must complete after Family Needs Researcher finishes. - This task must read Child UX Flow Designer before finalizing categories and metadata. - This task must complete before Agreement Template Builder finalizes printable layout and task labels. - QA and Launch Readiness Analyst cannot begin until this file exists. Inputs to read: - 00_team_brief.md - 01_family_needs_research.md - 02_child_ux_flow_design.md - 99_assumptions_decisions_log.md Output file: outputs/agent_teams_demo/interactive_screen_time_contract_builder/03_visual_task_icon_library.md Length: 1,300–1,800 words. Use exactly these sections: # Visual Task Icon Library ## Icon System Strategy Write 150–220 words describing visual style, child comprehension, and trustworthiness. ## Icon Design Principles List 10–14 principles covering simplicity, cultural neutrality, accessibility, print legibility, emotional tone, and age fit. ## Task Category Taxonomy Create 8–10 categories. For each include: Category Name, Purpose, Age Fit, Color/Shape Cue, Parent Explanation. ## Core Icon Library Create a table with at least 45 icons. Columns: Icon Name, Category, Suggested Visual, Child-Friendly Label, Parent Label, Age Range, Printable? Yes/No, Accessibility Alt Text. Include icons for hygiene, reading, homework, chores, meals, outdoor play, kindness, sleep, pet care, and family routines. ## Recommended Starter Sets Create starter icon bundles for ages 4–6, 7–9, and 10–12. Each bundle must include 8–12 icons. ## Custom Task Support Define how parents add custom tasks while preserving child-friendly language and printable clarity. ## Icon States Define default, selected, completed, locked, optional, and bonus states. Include visual and text cues. ## Risks and Misinterpretations List at least 8 icon risks and mitigations. ## Assumptions Challenged Challenge at least 2 assumptions from earlier files. State whether to keep, revise, or validate each. ## Handoff Notes for Agreement Template Builder Provide 8–12 requirements for labels, icon metadata, print behavior, and agreement wording. ## Handoff Notes for QA and Launch Readiness Analyst Provide 8–12 icon testing requirements. Update 99_assumptions_decisions_log.md: - Add at least 5 assumptions. - Add at least 4 decisions. - Add at least 3 open questions. Then run Agent 4. Agent 4: Agreement Template Builder Mission: Turn selected tasks, screen-time rules, rewards, and family names into a personalized downloadable and printable Family Screen Time Agreement. Dependency: - This task must complete after Family Needs Researcher, Child UX Flow Designer, and Visual Task Icon Curator finish. - This task must complete before QA and Launch Readiness Analyst begins. - Final synthesis cannot begin until this file exists. Inputs to read: - 00_team_brief.md - 01_family_needs_research.md - 02_child_ux_flow_design.md - 03_visual_task_icon_library.md - 99_assumptions_decisions_log.md Output file: outputs/agent_teams_demo/interactive_screen_time_contract_builder/04_agreement_template_builder.md Length: 1,500–2,100 words. Use exactly these sections: # Agreement Template Builder ## Template Strategy Summary Write 150–220 words explaining how the agreement becomes trustworthy, personal, and printable. ## Data Inputs Required Create a table with columns: Field, Required/Optional, User Who Provides It, Validation Rule, Used In Agreement Section. Include at least 20 fields. ## Agreement Generation Logic Describe rules for turning selected tasks and screen rules into agreement text. Include conditions for age, number of tasks, screen-time amount, bonus rewards, blackout times, and parent approval. ## Printable Agreement Structure Define the final document with exactly these sections: 1. Family Title 2. Our Screen Time Promise 3. Before Screens, I Will 4. Screen Time Rules 5. Bonus Ways to Earn Extra Time 6. What Happens If Tasks Are Not Done 7. Parent Promise 8. Child Promise 9. Signatures 10. Review Date For each section include purpose, dynamic fields, sample wording, and print layout notes. ## Download Formats Specify requirements for PDF, print view, and image export. Include filename conventions. ## Sample Generated Agreement Provide one complete sample agreement for a family with one child age 7. Keep it 350–500 words. ## Multiple Child and Sibling Logic Explain how to handle one agreement per child, shared family rules, fairness, and different ages. ## Parent Editing Controls Define what parents can edit before download and what should remain structured to avoid ambiguity. ## Privacy and Data Handling Specify minimal data collection, local/session storage assumptions, child privacy safeguards, and no unnecessary account requirement. ## Assumptions Challenged Challenge at least 2 assumptions from earlier files. State whether to keep, revise, or validate each. ## Handoff Notes for QA and Launch Readiness Analyst Provide 10–14 test requirements for template generation, print, download, wording, and edge cases. Update 99_assumptions_decisions_log.md: - Add at least 5 assumptions. - Add at least 5 decisions. - Add at least 3 open questions. Then run Agent 5. Agent 5: QA and Launch Readiness Analyst Mission: Test usability, accessibility, print formatting, mobile responsiveness, agreement generation, and edge cases before release. Dependency: - This task must complete after all previous agent outputs exist. - This task must complete before the synthesis/review step begins. Inputs to read: - 00_team_brief.md - 01_family_needs_research.md - 02_child_ux_flow_design.md - 03_visual_task_icon_library.md - 04_agreement_template_builder.md - 99_assumptions_decisions_log.md Output file: outputs/agent_teams_demo/interactive_screen_time_contract_builder/05_qa_launch_readiness.md Length: 1,400–1,900 words. Use exactly these sections: # QA and Launch Readiness ## QA Strategy Summary Write 150–220 words explaining the test approach. ## Critical User Journeys to Test List at least 8 journeys. For each include: Scenario, User Type, Success Criteria, Failure Risk. ## Functional Test Cases Create a table with at least 20 test cases. Columns: Test ID, Feature, Preconditions, Steps, Expected Result, Priority. ## Accessibility Test Plan Cover keyboard navigation, screen readers, color contrast, reduced motion, font sizing, plain language, touch targets, and print readability. Include at least 12 checks. ## Mobile and Responsive Test Plan Cover phone, tablet, desktop, portrait, landscape, low bandwidth, and touch interactions. Include at least 10 checks. ## Print and Download Test Plan Cover PDF generation, browser print, page breaks, grayscale, icon readability, signatures, no printer, and filename conventions. Include at least 12 checks. ## Edge Case Matrix Create a table with at least 15 edge cases. Columns: Edge Case, Impact, Expected Product Behavior, Severity, Owner. ## Content and Safety Review Review language for shame, conflict escalation, coercive framing, unrealistic expectations, and privacy concerns. Include required fixes. ## Launch Readiness Checklist Create a checklist with at least 25 items grouped by UX, Content, Accessibility, Technical, Privacy, Analytics, and Support. ## Assumptions Challenged Challenge at least 2 assumptions from earlier files. State whether to keep, revise, or validate each. ## Go/No-Go Recommendation State whether the product is ready for prototype testing, beta, or public launch. Include required blockers and nice-to-have improvements. ## Handoff Notes for Synthesis Review Provide 8–12 cross-functional findings. Update 99_assumptions_decisions_log.md: - Add at least 5 assumptions. - Add at least 5 decisions. - Add at least 4 open questions. Finally run the synthesis/review step. Synthesis/Review Owner: Team Lead Mission: Integrate the full pipeline into a coherent product direction, identify contradictions, resolve major open questions, and produce the final implementation-ready brief. Dependency: - This task must complete after QA and Launch Readiness Analyst finishes. - This is the final required step. Inputs to read: - All files in outputs/agent_teams_demo/interactive_screen_time_contract_builder/ - Especially 99_assumptions_decisions_log.md Output file: outputs/agent_teams_demo/interactive_screen_time_contract_builder/06_synthesis_review.md Length: 1,500–2,000 words. Use exactly these sections: # Synthesis Review ## Executive Summary Write 180–250 words summarizing the final product direction. ## Final Product Definition Define the tool in one paragraph and list the 10 most important product capabilities. ## Coherence Check Across Agents Create a table with columns: Area, Research Input, UX Decision, Icon/Template Decision, QA Concern, Final Resolution. Include at least 8 areas. ## Resolved Contradictions Identify at least 5 contradictions, tensions, or competing priorities across agent outputs. For each, explain the resolution. ## Final Recommended User Flow List the final 10–14 step user flow with concise descriptions. ## Final Agreement Requirements List the required agreement inputs, output sections, print/download requirements, and privacy constraints. ## MVP Scope Define what must be included in the first prototype. Include 15–25 bullets grouped by Must Have, Should Have, and Not Yet. ## Validation Plan Define how to test with parents and children. Include 5 research questions, 5 usability tasks, success metrics, and what evidence would cause redesign. ## Top Risks and Mitigations List the top 10 risks with mitigation plans. ## Implementation Handoff Provide a concise handoff for designers, developers, content writers, and QA. Include what each role should do next. ## Final Review Verdict State whether the concept is ready for prototype design, implementation planning, beta testing, or launch. Explain why. After writing 06_synthesis_review.md, update 99_assumptions_decisions_log.md one final time: - Mark any resolved open questions as resolved in the Suggested Resolution column. - Add final decisions from the synthesis. - Ensure every assumption has a confidence level and validation status. Completion requirements: - Confirm that all 8 files exist at the specified paths. - Ensure each file uses the exact section headings required. - Ensure every agent explicitly references prior agent outputs. - Ensure dependencies were followed in order. - Ensure the final synthesis/review step is completed. - Do not stop after partial completion.
Create your own AI agent team at Build Agents Store. Describe your business problem and get specialized agent teams with ready-to-use prompts for Claude Code.