@weave-tools/weave-it 0.1.1 → 0.1.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@weave-tools/weave-it",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "SDLC package for AI-assisted software teams working across monorepos and multi-repo workspaces.",
   "type": "module",
   "license": "MIT",

package/templates/skills/weave-architect/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: weave-architect
 description: Read-only thinking partner for active Weave architecture work. Use when the user wants engineering architecture, technical design, implementation strategy, tradeoff analysis, risk review, or a deep dive into an existing architecture facet.
-last_changed_in: 0.1.0
+last_changed_in: 0.1.3
 ---
 
 # Weave Architect
@@ -39,6 +39,7 @@ Do not write repo-tracked artifacts directly. Produce the plan, decisions, quest
 - Treat `weave-architect` as entering or resuming the architecture lane for the active change.
 - Treat `prd.md` as the preferred product contract when it exists and is useful, but do not require it before architecture thinking.
 - Read enough code, docs, ADRs, knowledge specs, and existing Weave artifacts to understand current implementation patterns before recommending design.
+- Read `.weave/architecture-considerations.md` when present and use it as user-owned team architecture guidance.
 - In workspace mode, inspect registered repo folders as implementation locations inside one shared change context. In repo mode, keep the resolved repo context as the boundary.
 - Support both legacy `wiki/changes/<change-id>/architecture.md` and folder-mode `wiki/changes/<change-id>/architecture/index.md` plus `architecture/*.md` facets.
 - If both `architecture.md` and `architecture/` exist, call out the conflict and ask the user to resolve it with `weave-clarify` or `weave-capture` before relying on either as canonical.
@@ -126,6 +127,7 @@ wiki/changes/<change-id>/architecture/*.md
 wiki/changes/<change-id>/sessions/*-architecture.md
 wiki/changes/<change-id>/knowledge-delta.md
 wiki/changes/<change-id>/tasks.md
+.weave/architecture-considerations.md
 ```
 
 Architecture shape rules:
@@ -137,6 +139,19 @@ Architecture shape rules:
 
 For session notes, prefer the latest `## Next Resume Point`, unresolved decisions, and explicit user preferences. If session notes contain `facets: [...]` frontmatter, use it to find relevant facet discussions, but do not require it.
 
+# Team Architecture Considerations
+
+If `.weave/architecture-considerations.md` exists, read it before making architecture recommendations.
+
+Treat this file as user-owned advisory guidance:
+
+- Do not edit it.
+- Do not quote it exhaustively.
+- Apply relevant guidance silently while reasoning.
+- Surface only constraints, conflicts, or risks that materially affect the design.
+- Do not treat examples as mandatory unless the file says they are.
+- If it conflicts with PRD context, ADRs, existing architecture, code reality, or explicit user instructions, call out the conflict and ask which source should be authoritative.
+
 # Codebase And Docs Context
 
 Inspect only context that can materially affect the architecture:
@@ -158,6 +173,7 @@ For relevant repos, prioritize reading:
 README.md
 CONTEXT.md
 CONTEXT-MAP.md
+.weave/architecture-considerations.md
 docs/**
 docs/adr/**
 adr/**