Multi-agentTechnology & Data AnalysisAdvancedFree

Software Development Planning System.

3 agents, 3 deliverables.

Run a multi-agent workflow to produce an execution-ready software development planning system deliverable.

WORKFLOW META
Agents3
Total tokens (avg)~500
Run time9 min
AI toolChatGPT Β· Claude Β· Gemini
Variables4
DifficultyAdvanced
CategoryTechnology & Data Analysis
SEQUENCE MAP Β· CLICK TO JUMP
Β· 01 Β·
Technical Requirements Analyst
Β· 02 Β·
Architecture Design Agent
Β· 03 Β·
Development Sprint Planner
USE CASE INPUTS

Set the workflow's inputs once.

These variables feed into every agent prompt below. Fill them once, then copy each agent in order.

{{software_project}}
Software project
Software project
Software Development Planning System example context
{{team}}
Team
Team
2 marketers, 1 designer, 1 developer
{{timeline}}
Timeline
Timeline
launching in 4 weeks
{{key_technical_challenge}}
Key technical challenge
Key technical challenge
Software Development Planning System example context
THE AGENTS

The 3-step sequence.

01
AGENT Β· TECHNICAL REQUIREMENTS

Technical Requirements Analyst

GOAL OF THIS STEP

Translate the project into technical requirements. Define: functional requirements (what the system must do β€” 10 user stories in the format 'As a [role], I want to [action], so that [benefit]'), non-functional requirements (performance targets, scalability ceiling, availability SLA, security requirements, browser/device support), technical constraints (existing infrastructure, technology mandates, budget for tools), and the definition of done (what must be true for the project to be considered complete).

EXPECTED OUTPUT

10 user stories + non-functional requirements + technical constraints + definition of done

agent-01-technical-requirements-analyst.md
### Input
Project, team, timeline, challenge

### Task
Translate the project into technical requirements. Define: functional requirements (what the system must do β€” 10 user stories in the format 'As a [role], I want to [action], so that [benefit]'), non-functional requirements (performance targets, scalability ceiling, availability SLA, security requirements, browser/device support), technical constraints (existing infrastructure, technology mandates, budget for tools), and the definition of done (what must be true for the project to be considered complete).

### Output
10 user stories + non-functional requirements + technical constraints + definition of done
02
AGENT Β· ARCHITECTURE DESIGN

Architecture Design Agent

03
AGENT Β· DEVELOPMENT SPRINT

Development Sprint Planner

HOW TO RUN

Three steps. 9 min.

STEP 01

Fill in the variables at the top. Copy them into a note or your tool's context window β€” every agent below uses them.

STEP 02

In your AI tool, paste Agent 1 and run it. Copy the output. Paste Agent 2 with the output appended. Repeat in order for all 3 agents.

STEP 03

At the final agent, review and refine. It outputs your finished deliverable, ready to publish or hand off.

WHAT YOU GET

The final output, end-to-end.

Technical Requirements Analyst

10 user stories + non-functional requirements + technical constraints + definition of done

Architecture Design Agent

Architecture pattern + full tech stack with justifications + data model + API design principles + integration list

Development Sprint Planner

Sprint-by-sprint plan: goal + stories + dependencies + acceptance criteria + team allocation + critical path

β˜… MULTI-AGENT PACK

The Multi-Agent Operator Pack.

100 production-ready workflows like this one. Agent prompts, variable cheat-sheets, and the operator's guide.

Free