メニュー
(forwward) Delivers technical strategy for architecture decisions, build-vs-buy analysis, tech stack selection, tech debt prioritization, and PRD writing. Triggers on architecture choices, technology evaluation, technical planning, or any CTO-level leadership question.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
(forwward) Runs lint, typecheck, build, and test in a self-healing loop that reads errors, fixes them, and retries up to 4 times. Triggers on verify, check, make sure it works, pre-commit validation, pre-deploy checks, or any quality gate.
(forwward) Ships code — owns the pipeline from verified branch to deployed and healthy. Stack-aware shipping engineer and on-call SRE: detects Node/Go/Python/Ruby/Rust/Java/Terraform/Pulumi/Lambda/CDK and runs the right gate, build, test, deploy. Three modes — PR, release (version bump, changelog, tag, health check), hotfix. Confirms before every irreversible step. Use for "ship this", "open a PR", "release", "deploy", "cut a release", "hotfix".
(forwward) Orchestrates multi-agent engineering and business teams by analyzing tasks, selecting team shapes, assigning specialist roles, and coordinating parallel agent work with skill dispatch. Triggers on tasks needing 2+ agents, feature dev with frontend + backend, quality audits, research sprints, bug hunts, or any work that benefits from parallel specialization.
(forwward) Consolidates recent team work — commits, PRs, decisions, fixes, learnings — into a shared `team-memory/MEMORY.md`. Like REM sleep for the team. Use after a PR merges, after a release, at sprint-end, or when the user says "team memory", "what did we ship this week". Reads git log, PRs, CHANGELOG, ADRs, and the conversation; appends Shipped, Decisions (with WHY), Fixes (root cause), Learnings, Open Threads. Not for one-off summaries or PII.
(forwward) Guides fullstack feature development with clean code patterns across any stack — TypeScript, Python, Go, Ruby, Java, Rust, and more. Detects the project's stack before advising. Triggers on implementing features, writing code, shipping UI + API + DB changes, or any hands-on engineering work.
(forwward) Onboards founders to forwward-teams by learning what they build, initializing the environment, and recommending which skills to use first. Triggers on first install, new project setup, getting started, or when a user asks what forwward-teams can do.
| name | cto |
| description | (forwward) Delivers technical strategy for architecture decisions, build-vs-buy analysis, tech stack selection, tech debt prioritization, and PRD writing. Triggers on architecture choices, technology evaluation, technical planning, or any CTO-level leadership question. |
Think like a technical co-founder. Every resource is an investment — what's the return?
Before committing resources:
Rule: If it doesn't serve top 3 priorities, it doesn't happen.
| Factor | Build | Buy |
|---|---|---|
| Core differentiator? | Build | — |
| Commodity? | — | Buy |
| Team expertise? | Build if yes | Buy if no |
| Time to market? | Slower | Faster |
| Long-term cost? | Lower if core | Lower if commodity |
Ask in order:
70% Core: Existing product, proven ROI
20% Adjacent: Related opportunities, emerging bets
10% Transformational: Future business, experiments
| Quadrant | Action |
|---|---|
| High impact, Low effort | Fix now |
| High impact, High effort | Schedule sprint |
| Low impact, Low effort | Fix opportunistically |
| Low impact, High effort | Never |
## Problem
What user pain are we solving? (1 sentence)
## Success Metric
How do we know it worked? (1 number)
## Scope
What's in / what's out?
## Approach
High-level technical direction (not implementation details)
## Risks
What could go wrong? Mitigation?
## Timeline
Milestones with dates. One-way doors flagged.
| Audience | Lead With | Support With |
|---|---|---|
| Board | Outcomes, risks, asks | Metrics, plans |
| Engineers | Why, context, constraints | Technical details |
| Product | Trade-offs, timelines | Alternatives considered |