ship-architect
Skill1 starsChanged 7 months agoMITView on GitHub
Define system architecture from approved PRD and research. Produces architecture doc, data model, API contracts, ADRs. Requires user approval. Must run after ship-spec.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nathfavour/shiptheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nathfavour/ship★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- accessibilitySkill
- agent-evalSkill
- agentic-engineeringSkill
- ai-regression-testingSkill
- api-designSkill
- atomic-planningSkill
- backend-patternsSkill
- coding-standards-eccSkill
- context-engineeringSkill
- frontend-patternsSkill
- git-worktreesSkill
- langchain-dependenciesSkill
- langchain-fundamentalsSkill
- langchain-middlewareSkill
- langchain-ragSkill
- langgraph-fundamentalsSkill
- langgraph-persistenceSkill
- minimalist-skillSkill
- output-skillSkill
- redesign-skillSkill
- security-scanSkill
- ship-autoSkill
- ship-bugfixSkill
- ship-deploySkill
- ship-discoverSkill
- ship-executeSkill
- ship-finish-branchSkill
- ship-newSkill
- ship-planSkill
- ship-researchSkill
- ship-resumeSkill
- ship-reviewSkill
- ship-settingsSkill
- ship-specSkill
- ship-statusSkill
- ship-testSkill
- ship-worktreeSkill
- soft-skillSkill
- systematic-debuggingSkill
- taste-skillSkill
- test-driven-developmentSkill
- two-stage-reviewSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Read PRD.md + RESEARCH.md + PROJECT.md.
- Very specific: line 30
Create .claude/state/ROADMAP.md — phases ordered by dependency from the PRD.
- Distinctive: line 32
After approval, present build mode selection:
- Very specific: line 39
Update progress.json: set phases.architecture.status to "approved".
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Architecture — System design
Pre-condition
.claude/state/PRD.md must exist and be approved (check progress.json).
Process
- Read PRD.md + RESEARCH.md + PROJECT.md.
- Produce ARCHITECTURE.md with:
- Tech stack with rationale for each choice
- System architecture (component-level: frontend, backend, database, external services)
- Data model (full schema definitions with types, relations, constraints)
- API endpoints (method, path, request/response shape, auth requirements)
- Infrastructure layout (hosting: Railway, Vercel, Supabase, etc.)
- Architecture Decision Records for non-obvious choices:
ADR-001: [Decision title] Context: [Why this decision was needed] Decision: [What was decided] Rationale: [Why this option over alternatives] Consequences: [What this means for implementation]
- Save to
.claude/state/ARCHITECTURE.mdand.claude/state/decisions.md. - Create
.claude/state/ROADMAP.md— phases ordered by dependency from the PRD. - Present architecture to the user for approval (approve / adjust).
After approval, present build mode selection:
"How do you want to proceed with implementation? A. Guided mode (default) — I plan each phase and wait for your go. B. Autonomous mode — I build everything without stopping. /bayes-ship:ship-auto C. Semi-autonomous — I pause between phases for a checkpoint. /bayes-ship:ship-auto --checkpoints"
- Update progress.json: set
phases.architecture.statusto"approved". - Output next step based on user's build mode choice.
Gate
User MUST explicitly approve architecture before any implementation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

