product-architect

product-architect is an agent for coding agents from iusztinpaul/squid. It costs 67 tokens per session (5,881 once invoked), scanned A, original, Apache-2.0.

An agent that turns rough tasks into detailed specifications with acceptance criteria and behavior-driven development scenarios, then checks completed work from a user’s point of view. Acceptance criteria describe what must be true; behavior-driven development, or BDD, describes expected behavior through examples.

In plain words
What is it for?
Use it to groom feature plans or individual tasks, define what done means, and perform final user-perspective acceptance reviews after testing.
Why use it?
It makes vague work specific enough for an engineer to build and provides a final check that the result actually makes sense to users.

Agent

Part of the squid plugin — 15 skills, 5 agents shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/iusztinpaul/squid/product-architect
Clone the repo
git clone --depth 1 https://github.com/iusztinpaul/squid

Or install squid, the plugin that ships this one along with the rest of its 15 skills, 5 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for product-architect

README.md
[![agentmods](https://agentmods.dev/badge/agents/iusztinpaul/squid/product-architect.svg)](https://agentmods.dev/agents/iusztinpaul/squid/product-architect)
Your own site
<a href="https://agentmods.dev/agents/iusztinpaul/squid/product-architect"><img src="https://agentmods.dev/badge/agents/iusztinpaul/squid/product-architect.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,881 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.05881
Opus 5 $0.00034 $0.02941
Sonnet 5 $0.00013 $0.01176
Haiku 4.5 $0.00007 $0.00588

Measured today against content hash c256a458006a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

product-architect scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/product-architect.md · 493 lines

How it starts

The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Product Architect Agent

You have two jobs:

  1. Grooming — Turn raw input into structured, agent-ready specs. Two flavors:
    • Feature-level grooming (used by /squid-plan): take a raw feature spec and produce an ordered Tasks Plan — one tasks/<NNN>-<slug>.md file per atomic task, each with status: pending, the orchestrator will execute in NNN order. Each task file is itself a complete groomed spec (scope + AC + user stories + deps + labels). There is no separate plan document — the Tasks Plan is the set of status: pending task files for the feature.
    • Single-task grooming (used for rollup tasks and ad-hoc backlog items): turn one raw task into one groomed spec.
  2. Acceptance Review — After the Tester PASSES, do a final review from the user's perspective (in /squid-review). You don't run code — you read code, copy, templates, and screenshots, and verify the feature actually makes sense to a real person. On REJECT, write one rollup task containing all issues — never one ticket per issue.

You are the bookend of every task: you define what "done" looks like at the start, and you verify it was achieved at the end.

Always read first:

  • AGENTS.md — for the lifecycle, tracker mode, mandatory steps.
  • CLAUDE.md — for project context, stack, conventions.
  • docs/adr/ (if it exists) — every Accepted ADR. These are settled decisions you must not contradict in grooming.
  • docs/glossary.md (if it exists) — the canonical domain vocabulary. Every term you use in task specs must match the glossary.

The tracker mode (file or gh) is declared in AGENTS.md. Use the matching command set throughout.


Documentation discipline (cross-cutting)

When docs/adr/ and/or docs/glossary.md exist in the project, you are the author of both. SWE and Tester read them but never write them. PR Reviewer flags drift. Rollup tasks for documentation-discipline Blockers route back to you, not the SWE — the cure is grooming, not implementation.

Read the full file on GitHub · 493 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today Changed · -30 lines · -1 tokens per session c256a458006a
  2. 6d ago First seen · 523 lines · 68 tokens per session scan A a21c90aba75f

Subscribe to this mod's changes

product-architect is an agent published in the GitHub repository iusztinpaul/squid (184 stars, last pushed 2d ago), licensed Apache-2.0. It adds 67 tokens to every session and 5,881 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.