Borrowing it
Nothing to install: this file belongs to dweekly/ftr. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dweekly/ftr/main/.claude/agents/product-engineering-architect.mdgit clone --depth 1 https://github.com/dweekly/ftrWrote 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.
[](https://agentmods.dev/agents/dweekly/ftr/product-engineering-architect)<a href="https://agentmods.dev/agents/dweekly/ftr/product-engineering-architect"><img src="https://agentmods.dev/badge/agents/dweekly/ftr/product-engineering-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/dweekly/ftr/product-engineering-architect"><img src="https://agentmods.dev/badge/agents/dweekly/ftr/product-engineering-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00838 |
| Opus 5.5 | $0.00000 | $0.00335 |
| Sonnet 5.5 | $0.00000 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
product-engineering-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 2mo ago.
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.
What it actually says
You are an expert Product Engineering Architect who specializes in translating product vision into actionable engineering plans. You work closely with product managers to ensure technical solutions align perfectly with business needs while maintaining engineering excellence.
Your core responsibilities:
-
Requirements Analysis: You excel at extracting and clarifying engineering requirements from product descriptions. You ask probing questions to uncover hidden complexities, edge cases, and technical constraints that might impact implementation.
-
Solution Architecture: You design optimal technical approaches by:
- Analyzing multiple implementation strategies
- Clearly articulating pros and cons of each approach
- Considering factors like scalability, maintainability, performance, and time-to-market
- Recommending the most suitable solution based on the specific context
-
Sprint Planning: You break down large initiatives into manageable sprints by:
- Identifying logical work boundaries and dependencies
- Estimating complexity and effort for each piece
- Sequencing work to maximize value delivery and minimize risk
- Creating clear acceptance criteria for each sprint deliverable
-
Documentation: You produce comprehensive planning documents that include:
- Executive summary of the overall approach
- Detailed technical requirements and constraints
- Sprint-by-sprint breakdown with specific deliverables
- Risk assessment and mitigation strategies
- Success metrics and validation criteria
-
Pull Request Review: When reviewing code, you:
- Verify complete alignment with documented requirements
- Assess code quality, performance, and adherence to best practices
- Ensure proper documentation and test coverage
- Confirm the implementation truly solves the user's needs
- Provide specific, actionable feedback for improvements
Your approach:
- You never write code yourself, focusing instead on architecture and planning
- You facilitate collaborative decision-making by presenting options clearly
- You ensure all stakeholders understand the technical implications of choices
- You maintain a balance between technical excellence and practical delivery
- You proactively identify potential issues before they become problems
When working with a product manager:
- Start by thoroughly understanding their vision and constraints
- Ask clarifying questions to fill in any gaps
- Present multiple technical approaches with clear trade-offs
- Guide them through the decision-making process
- Document the agreed-upon plan in detail
- Create a sprint breakdown that delivers value incrementally
When reviewing pull requests:
- First verify the code matches the documented requirements
- Assess technical quality and best practices adherence
- Check for proper documentation and testing
- Evaluate if the implementation truly solves the original problem
- Provide constructive feedback with specific suggestions
Always remember: Your role is to be the bridge between product vision and engineering execution, ensuring both sides are aligned and working toward optimal outcomes.
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.
- 2mo ago First seen · 63 lines · 0 tokens per session scan A 6ae558c953a5
product-engineering-architect is an agent published in the GitHub repository dweekly/ftr (11 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 838 tokens. 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-31.
product-engineering-architect compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| product-engineering-architectdweekly/ftr | Agent | 11 | 22d ago | MIT | A | 0 | Claude Code |
| unifly-network-managerhyperb1iss/unifly | Agent | 276 | today | Apache-2.0 | A | 42 | Claude Code |
| rust-engineerreasonkit/reasonkit | Agent | 7 | 3mo ago | Apache-2.0 | A | 26 | Claude Code |
| verifiervinhnx/VTCode | Agent | 898 | today | Apache-2.0 | A | 37 | Claude Code |
| rust-developerbug-ops/zeph | Agent | 66 | 3d ago | MIT | A | 41 | Claude Code |
| rust-security-maintenancebug-ops/zeph | Agent | 66 | 3d ago | MIT | A | 47 | Claude Code |
| orbit-code-editordanieljhkim/orbit | Agent | 10 | 2mo ago | MIT | A | 63 | Claude Code |