smithery.ai

project-architect

Turn a freeform brief into a concrete build plan: requirements, tasks, skill opportunities, runbook, risks, acceptance. Use when asked to plan a feature/project, refine IMPLEMENTATION_PLAN.md, or create a skills blueprint before building.

First seen Mar 22, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,587 B
  • docs SUMMARY.md 263 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Project Architect

Output Contract

Produce a plan that is immediately executable, with:

  • Requirements (functional + non-functional)
  • Task breakdown (small, dependency-aware)
  • Skill opportunities (what to automate/templatize)
  • Runbook (commands + expected artifacts)
  • Risks / unknowns / decision points
  • Acceptance tests (verifiable)

Steps

  1. Extract requirements

- What must exist when done? - What must NOT change? - Edge cases and failure modes.

  1. Decompose into tasks

- Right-size: one agent iteration per task. - Separate investigation from implementation. - Include required tests/checks per task (what to verify).

  1. Identify skill opportunities

- Look for repeated patterns that will recur across tasks. - Propose minimal new skills (avoid over-forging). - For each candidate skill, provide: - name, type (operational|meta|composed) - 1-2 sentence description (with triggers) - inputs/outputs - example prompts

  1. Write runbook + acceptance

- Commands to run locally (build/test/lint/typecheck). - Acceptance checks that are machine-verifiable when possible.

Notes

  • If this project uses Forgeloop: keep the plan aligned with IMPLEMENTATION_PLAN.md and Forgeloop's “single unit of work” iteration model.