Human Architect Mindset
Apply SDD and constitution checklists so specs, structure, and anti-patterns stay explicit before and during implementation.
Overview
human-architect-mindset is a journey-wide agent skill that encodes SDD constitution and architecture checklists—usable whenever a solo builder needs to lock rules before committing agent-generated code.
Install
npx skills add https://github.com/bencium/bencium-marketplace --skill human-architect-mindsetWhat is this skill?
- Phase SDD-1 Constitution Definition checklist for stack, directories, coding standards, anti-patterns, and security
- Tech stack constitution requires exact language and framework versions
- Anti-patterns constitution pairs forbidden patterns with detection methods
- Human Architect Mindset checklists per phase of architectural thinking
- Supports Spec Driven Development extension for superhuman code quality
- Phase SDD-1 Constitution Definition checklist with five constitution sections (tech stack, directories, coding standards
- Five verification bullets under Tech Stack Constitution alone
Adoption & trust: 1.1k installs on skills.sh; 273 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps inventing stack choices, folder chaos, and forbidden patterns because the project never wrote a constitution.
Who is it for?
Indie builders running long-lived agent sessions who want spec-driven constitutions before implementation and during reviews.
Skip if: One-off scripts with no ongoing codebase or teams that already maintain a formal architecture decision record outside the agent.
When should I use this skill?
Establishing or auditing project constitution, SDD phases, directory law, coding standards, anti-patterns, and security rules before or during agent-assisted development.
What do I get? / Deliverables
You get phase-by-phase SDD checklists with explicit versions, structures, anti-patterns, and security rules agents can enforce on every change.
- Completed SDD constitution checklists (stack, structure, standards, anti-patterns, security)
- Phase-aligned architectural audit notes for agent enforcement
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Before greenlighting an MVP, run SDD-1 to document exact framework versions and forbidden libraries.
Mid-sprint, verify directory structure and test file locations against the constitution checklist.
Pre-merge, audit whether new code violates listed security or performance anti-patterns with detection steps.
When onboarding a new agent session, re-load constitution rules so refactors do not erode logging or import standards.
How it compares
Constitution and checklist discipline for agents, not a feature generator or infra deploy skill.
Common Questions / FAQ
Who is human-architect-mindset for?
Solo and indie builders who act as the human architect while agents write code and need SDD-style guardrails.
When should I use human-architect-mindset?
At Validate scope when defining constitutions, during Build when enforcing directory and coding law, and at Ship review when checking anti-patterns and security rules.
Is human-architect-mindset safe to install?
It is checklist-only guidance with no network calls; review the Security Audits panel on this Prism page for the marketplace package source.
SKILL.md
READMESKILL.md - Human Architect Mindset
# Human Architect Mindset - Checklists Practical audit checklists for each phase of architectural thinking. --- ## Spec Driven Development Checklists The following checklists support the SDD extension for superhuman code quality. --- ## Phase SDD-1: Constitution Definition Checklist Use when establishing unbreakable rules for a project. ### Tech Stack Constitution - [ ] Languages specified with exact versions? - [ ] Frameworks specified with exact versions? - [ ] Database and infrastructure choices documented? - [ ] Required libraries listed with versions? - [ ] Forbidden libraries listed with reasons? ### Directory Structure Constitution - [ ] Top-level directory structure documented? - [ ] File naming conventions specified? - [ ] Component organization patterns defined? - [ ] Test file locations standardized? - [ ] Configuration file locations fixed? ### Coding Standards Constitution - [ ] Naming conventions defined (files, variables, functions, classes)? - [ ] Error handling patterns specified? - [ ] Logging standards documented? - [ ] Import ordering rules set? - [ ] Comment/documentation requirements established? ### Anti-Patterns Constitution - [ ] Forbidden patterns listed with reasons? - [ ] Security anti-patterns explicitly prohibited? - [ ] Performance anti-patterns documented? - [ ] Architectural anti-patterns named? - [ ] Each anti-pattern has detection method? ### Security Constitution - [ ] Authentication requirements specified? - [ ] Authorization model defined? - [ ] Input validation requirements documented? - [ ] Encryption standards set (at-rest, in-transit)? - [ ] Secret management rules established? ### Performance Constitution - [ ] Latency budgets defined (p50, p95, p99)? - [ ] Memory limits specified? - [ ] Bundle size budgets set? - [ ] Database query limits documented? - [ ] API rate limits established? ### Testing Constitution - [ ] Coverage minimums set (unit, integration, e2e)? - [ ] Test naming conventions defined? - [ ] Mock/stub policies established? - [ ] CI/CD gate criteria specified? - [ ] Test data management rules set? **Exit criteria:** Every rule in the constitution is machine-enforceable or has explicit human review point. --- ## Phase SDD-2: Blueprint Creation Checklist Use when creating specifications before implementation. ### Functional Specification - [ ] All user stories written in standard format? - [ ] Every story has acceptance criteria? - [ ] Requirements have unique IDs (REQ-DOMAIN-###)? - [ ] Edge cases documented for each requirement? - [ ] Error states explicitly defined? - [ ] Non-functional requirements have metrics? ### Technical Specification - [ ] Architecture diagram created? - [ ] Data models have exact field types and constraints? - [ ] API contracts fully defined (request/response schemas)? - [ ] Component contracts have exact method signatures? - [ ] Error handling documented per component? - [ ] Performance budgets assigned per component? ### Task Specification - [ ] Tasks are atomic (one conceptual change)? - [ ] Each task has `input_context_files` list? - [ ] Each task has `definition_of_done` with signatures? - [ ] Task dependencies form valid DAG (no cycles)? - [ ] Layer ordering enforced (foundation → logic → surface)? - [ ] Each task has verification commands? ### Traceability Matrix - [ ] Every requirement has corresponding task(s)? - [ ] Every task traces to requirement(s)? - [ ] No requirements have empty "Covered by Task" column? - [ ] Test cases link to requirements they validate? - [ ] Traceability matrix passes automated checks? ### Blueprint Completeness - [ ] Intent documents exist for major features? - [ ] All acceptance criteria are testable? - [ ] No ambiguous language ("fast", "secure", "simple")? - [ ] All domain terms defined in glossary? - [ ] Examples provided for complex requirements? **Exit criteria:** Traceability matrix shows 100% coverage from requirements to tasks. --- ## Phase SDD-3: Superhuman Output Verific