Menu
NEW AGENT
MY AGENTS
ASSISTANTS
Step 1:
Write Software Spec & Mockups
1️⃣
Perfect output
- scan ALL
2️⃣ Add
output numbers
, then...
3️⃣ Add
Subagent Numbers
(work backwards
from output number!
)
4️⃣ Add
ACTUAL Skills
to subagent
✅ DONE..Copy x4 to Step 3...
SETTINGS
LOGOUT
What Shall We Build Next?
1
Describe
Describe your task
2
Refine
Refine the plan
3
SubAgents
Review all agents
4
Deploy
Deploy your agent
Sub Agent 1
Sub Agent 2
Sub Agent 3
Sub Agent 4
Sub Agent 5
Sub Agent 6
Sub Agent 7
Sub Agent 8
A) SUBAGENT SUMMARY: BrainstormingAgent brainstorms potential implementation methods, APIs, libraries, and SDKs for the cloud-based software based on the initial input. B) FINAL TASK OUTPUT: A text file containing a list of 3-5 potential implementation methods, APIs, libraries, and SDKs, each with a brief description (50-100 words) of how they could be used in the project. The text file should be saved in HTML format for easy integration into the final specification document. C) SUBAGENT INPUT: - Initial project description (name of the tool and a rough description of what it will do) - List of potential APIs/libraries to consider (if available) D) SUBAGENT TASK SUMMARY: 1. Input: Initial project description and potential APIs/libraries 2. Skill #181 - Research Topic (Or Keyword) Deeply: Conduct in-depth research on the project topic and the suggested APIs/libraries 3. Skill #184 - Brainstorm Related Keywords: Generate related keywords and concepts based on the research findings 4. Skill #178 - Rewrite Text Based On Instructions: Analyze the research findings and brainstormed keywords to generate a list of 3-5 potential implementation methods, APIs, libraries, and SDKs 5. Skill #178 - Rewrite Text Based On Instructions: Provide a brief description (50-100 words) for each suggested method, API, library, or SDK, explaining how it could be used in the project 6. Skill #168 - Save text/html to server: Save the list of potential implementation methods, APIs, libraries, and SDKs, along with their descriptions, as an HTML file 7. Output: URL of the saved HTML file containing the list of potential implementation methods, APIs, libraries, and SDKs, with brief descriptions E) SILOS: This subagent does not require silos, as the tasks can be completed sequentially without the need for parallel processing or complex dependencies.
SubAgent #1 - Diagram
Expand Diagram
A) SUBAGENT SUMMARY: ResearchAgent conducts deep and light research on suggested APIs/libraries, investigates their compatibility with Bubble, and compiles the findings into a document. B) FINAL TASK OUTPUT: A text document (up to 5000 characters) containing researched materials on the suggested APIs/libraries and their compatibility with Bubble, saved as a .txt file on the server. C) SUBAGENT INPUT: - A list of 3-5 potential APIs, libraries, and SDKs suggested by the BrainstormingAgent D) SUBAGENT TASK SUMMARY: 1. Retrieve list of suggested APIs/libraries from BrainstormingAgent output (Skill #236) 2. For each API/library in the list: a. Conduct deep research on the API/library (Skill #181) b. Conduct light research on the API/library (Skill #182) c. Investigate compatibility with Bubble (Skill #182) d. Combine research findings into a single text block (Skill #220) 3. Compile all research findings into a single document (Skill #220) 4. Save the final research document as a .txt file on the server (Skill #168) E) SILOS: Silo 1: API/Library Research - Retrieve list of suggested APIs/libraries from BrainstormingAgent output (Skill #236) - For each API/library in the list: - Conduct deep research on the API/library (Skill #181) - Conduct light research on the API/library (Skill #182) - Investigate compatibility with Bubble (Skill #182) - Combine research findings into a single text block (Skill #220) Silo 2: Compilation and Saving - Compile all research findings into a single document (Skill #220) - Save the final research document as a .txt file on the server (Skill #168)
SubAgent #2 - Diagram
Expand Diagram
A) SUBAGENT SUMMARY: SelectionAgent analyzes the research output from ResearchAgent and selects the best 2-3 APIs/libraries to be used for the software. B) FINAL TASK OUTPUT: A finalized list of 2-3 APIs/libraries to be used for the software, saved as a text file (approximately 500-1000 characters). C) SUBAGENT INPUT: - Research output from ResearchAgent (a document containing researched materials on the suggested APIs/libraries and their compatibility with Bubble) E) SUBAGENT TASK SUMMARY: 1. Extract content of ResearchAgent's output file (#236) 2. Analyze the research output and evaluate APIs/libraries based on features, compatibility, and suitability for the project (#178) 3. Select the best 2-3 options from the analyzed APIs/libraries (#178) 4. Generate a finalized list of the selected APIs/libraries, including a brief description of each and the reasons for their selection (#178) 5. Format the finalized list as a text document (#178) 6. Save the formatted list to the server (#168) F) SILOS: This subagent does not require silos as the tasks can be completed sequentially without the need for parallel processing or sub-divisions.
SubAgent #3 - Diagram
Expand Flow
A) SUBAGENT SUMMARY: DesignAgent selects and provides commentary on the most suitable template pages for the desired software functionality. B) FINAL TASK OUTPUT: - 3-4 selected HTML template pages (each HTML file size: 50-100 KB) - A text file containing a commentary on necessary edits for each selected template page (text file size: 1-2 KB) C) SUBAGENT INPUT: - A folder URL containing the provided HTML template pages - A description of the desired software functionality and requirements E) SUBAGENT TASK SUMMARY: 1. Input folder URL and desired software functionality > #186 - Select Most Relevant Images From External Server 2. Selected template pages > #198 - Analyze An Image With GPT Vision & Return Text 3. Analyzed template pages and desired functionality > #178 - Rewrite Text Based On Instructions 4. Commentary on necessary edits > #168 - Save text/html to server 5. Selected template pages and commentary text file > #215 - Summarise and Return All Final Output Files F) SILOS: Silo 1: Template Selection - Input folder URL and desired software functionality > #186 - Select Most Relevant Images From External Server - Selected template pages > #198 - Analyze An Image With GPT Vision & Return Text Silo 2: Commentary Generation - Analyzed template pages and desired functionality > #178 - Rewrite Text Based On Instructions - Commentary on necessary edits > #168 - Save text/html to server Silo 3: Output Preparation - Selected template pages and commentary text file > #215 - Summarise and Return All Final Output Files
4 Template & Links
Expand Flow
A) SUBAGENT SUMMARY: The MockupEditingAgent edits the selected HTML design mockup pages based on the DesignAgent's commentary and saves the edited pages. B) FINAL TASK OUTPUT: - 3-4 edited HTML design mockup pages - Each HTML file size: 50-100 KB - The edited pages should reflect the desired functionality and design as per the DesignAgent's commentary - The pages should be ready for a Bubble developer to translate into a working application C) SUBAGENT INPUT: - Selected HTML template pages from the DesignAgent - Commentary on necessary edits from the DesignAgent E) SUBAGENT TASK SUMMARY: 1. Download Selected HTML Template Pages (Skill #174) - Input: URLs of the selected HTML template pages from the DesignAgent - Output: Downloaded HTML files saved on the server 2. Extract Content of HTML Files (Skill #236) - Input: URLs of the downloaded HTML files - Output: Extracted HTML content 3. Rewrite HTML Based On Instructions (Skill #179) - Input: Extracted HTML content and DesignAgent's commentary on necessary edits - Output: Edited HTML content 4. Save Edited HTML Pages (Skill #168) - Input: Edited HTML content - Output: Edited HTML pages saved on the server (3-4 files, each 50-100 KB in size) 5. Summarise and Return All Final Output Files (Skill #215) - Input: URLs of the edited HTML pages - Output: Summary of the edited HTML pages, including their URLs (both internal and external) F) SILOS: This subagent does not require silos as the tasks are sequential and interdependent. Each step's output becomes the input for the next step, forming a linear workflow.
5 Template & Links
Expand Flow
A) SUBAGENT SUMMARY: SpecificationAgent generates a comprehensive technical specification document in HTML format based on the provided APIs/libraries and design mockups. B) FINAL TASK OUTPUT: - A comprehensive technical specification document in HTML format (estimated size: 10-20 pages, approximately 5,000-10,000 words) C) SUBAGENT INPUT: - Examples/templates of previous specification documents - Selected APIs/libraries - Edited design mockups E) SUBAGENT TASK SUMMARY: subagent final input(s) > #174 - Copy & Download External File (for example/template specs) > #177 - Write Text (Or Copy) From Researched Text (to analyze selected APIs/libraries and edited design mockups) > #178 - Rewrite Text Based On Instructions (to write introduction section) > #177 - Write Text (Or Copy) From Researched Text, #178 - Rewrite Text Based On Instructions, #179 - Rewrite HTML Based On Instructions (to detail technical process, functionality, user flows, data structures, and logic) > #179 - Rewrite HTML Based On Instructions (to explain each designed mockup page and link visual elements to functionality) > #178 - Rewrite Text Based On Instructions, #179 - Rewrite HTML Based On Instructions (to edit, review, and finalize each section of the document) > #168 - Save text/html to server (to save final document) > #215 - Summarise and Return All Final Output Files > subagent final output(s) F) SILOS: Silo 1: Researching and Analyzing - #174 - Copy & Download External File (for example/template specs) - #177 - Write Text (Or Copy) From Researched Text (to analyze selected APIs/libraries and edited design mockups) Silo 2: Writing Introduction - #178 - Rewrite Text Based On Instructions (to write introduction section) Silo 3: Detailing Technical Aspects - #177 - Write Text (Or Copy) From Researched Text, #178 - Rewrite Text Based On Instructions, #179 - Rewrite HTML Based On Instructions (to detail technical process, functionality, user flows, data structures, and logic) Silo 4: Explaining Design Mockups - #179 - Rewrite HTML Based On Instructions (to explain each designed mockup page and link visual elements to functionality) Silo 5: Editing and Finalizing - #178 - Rewrite Text Based On Instructions, #179 - Rewrite HTML Based On Instructions (to edit, review, and finalize each section of the document) - #168 - Save text/html to server (to save final document) Silo 6: Summarizing and Returning Output - #215 - Summarise and Return All Final Output Files
6 Template & Links
Expand Flow
Templates & Links Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
7 Template & Links
Expand Flow
Questions & Research Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
8 Template & Links
Expand Flow
Templates & Links Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
9 Template & Links
Expand Flow
Templates & Links Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
10 Template & Links
Expand Flow
Questions & Research Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
11 Template & Links
Expand Flow
Templates & Links Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
12 Template & Links
Expand Flow
Need To Start Afresh?
BACK TO REFINE
Tweaked & Good To Go?
PROCEED TO DEPLOY
