Core
Workflow templates
The PWR workflow library and agent roles, what each template actually launches, and which gates the platform enforces.
A workflow template turns an intent, such as "fix a bug" or "plan a sprint", into a concrete launch: a task, a goal, a planning conversation or a sprint execution. Each template is tied to an agent role. You find templates on the PWR Studio Home launcher and under Workflows.
Status: The role and template library is implemented and tested up to the point of launch: a created task, a started goal or a pending run. Templates do not add new execution machinery; everything they launch runs through the same task, review and approval workflow as any other work.
Agent roles
A role is a template for an agent: responsibilities, a prompt suffix, a tool policy, the kinds of run it is meant for, and the deliverable it should produce. An agent is the executable binding of a role to a provider and model.
| Role | Tools | Used for | Declared gates |
|---|---|---|---|
| Producer | Read-only | Planning, chat | Applying a plan as tasks needs approval |
| QA / SDET | Read, write, shell | Planning, implementation, review | Changing production code needs approval |
| Gameplay Engineer | Full sandbox, shell | Implementation, review | Merge needs approval |
| Software Engineer | Full sandbox, shell | Planning, implementation, review | Merge needs approval |
| Game Designer | Read-only | Planning, chat | Changing an approved design needs approval |
| Technical Artist | Full sandbox, shell | Implementation | Replacing binary assets needs approval |
| DevOps / Build | Full sandbox, shell | Implementation, review | Deploying is forbidden |
| Security Engineer | Read-only plus shell | Review, implementation | Disabling a control is forbidden |
| Release Manager | Read-only | Chat, review | Deploying and merging are forbidden |
What is enforced and what is declared
Gates and deliverable formats are written into the agent's instructions. The platform enforces the ones it has mechanisms for:
- the tool allowlist and the shell switch in the agent's tool policy;
- the merge gate and commit-bound human approvals. See GitHub integration;
- "forbidden to deploy" holds because no deploy capability exists in the sandbox, not because of wording in a prompt.
Structured deliverables are validated only for plan and review output. The other deliverable formats are instructions to the agent, not something the platform checks. There is no per-action policy engine.
Templates
| Template | Launches | Role | What happens |
|---|---|---|---|
| Start a New Game | Goal | Gameplay Engineer, planned by Producer | A planning run produces a plan; you approve it; tasks follow. Only for a new or empty repository. |
| Build a Feature | Task | Software Engineer or Gameplay Engineer | A ready task with acceptance criteria. You queue it. |
| Fix a Bug | Task | Software Engineer | A high-priority task with a "regression test first" criterion. |
| Analyze an Existing Repository | Conversation | Producer | A read-only run; the architecture summary is the reply. |
| Improve Test Coverage | Coverage run | QA / SDET | Starts the Test Coverage Autopilot. |
| Generate Unit Tests | Task | QA / SDET | A task scoped to tests only. |
| Create a Test Plan | Conversation | QA / SDET | A read-only run that returns a test plan. |
| Review a GDD | Conversation | Game Designer | A read-only review of a design document. Game projects only. |
| Plan a Sprint | Conversation (plan) | Producer | Returns a plan you can apply as tasks; can also create a planned sprint. |
| Execute a Sprint | Sprint execution | none | Runs selected sprint tasks as a goal. Needs an active sprint. |
| Reduce Technical Debt | Conversation (plan) | Software Engineer | Returns a backlog to apply as tasks. |
| Prepare a Release | Conversation | Release Manager | A readiness checklist from recorded evidence. Never merges, tags or deploys. |
| Build an API | Task or goal | Software Engineer | One task, or a goal for a multi-endpoint surface. |
| Refactor a Codebase | Goal | Software Engineer | A goal that starts with a planning run. |
| Create a CI Pipeline | Task | DevOps / Build | A task. Deployment steps are described, never automated. |
| Custom Task | Task | none | A task whose model is chosen by PWR Auto. |
Launching a template
- Choose a template and a project. Developers and above can launch.
- Fill in the inputs. They are validated; invalid inputs are refused with
template_inputs_invalid. - Review the pre-flight estimate: a credit range and the model route. See Billing and credits.
- Launch.
PWR picks the agent you named, or your organization's first enabled agent with the template's role. If none exists, an agent is created from the role and the response says so. Both paths are audited.
A refused launch creates nothing.
Availability rules
A template can be unavailable for a project. PWR Studio shows the reason.
| Rule | Available when |
|---|---|
| Needs a workspace source | The project has a connected repository or a workspace source |
| Needs a GitHub connection | The project has a repository connection |
| Needs a new or empty repository | No repository is connected, or the connected one is empty |
| Needs a game project | The project type is game |
| Needs a game profile | Engine discovery has run for the project |
| Needs Jira | A Jira connection is linked to the project |
| Needs an active sprint | The project has an active sprint |
Rules are checked again at launch, which returns 409 template_unavailable with the reason.
Customising
Roles and templates are versioned. The platform ships defaults. An admin can clone a default into the organization and edit the copy; each edit creates a new version. Your organization uses its own latest active version when one exists, otherwise the platform default.
Template prompts use simple placeholder substitution. There is no templating language.