swe-workflow-skills 0.11.0 → 0.11.2

package/VERSION

@@ -1 +1 @@
-0.11.0
+0.11.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "swe-workflow-skills",
-  "version": "0.11.0",
+  "version": "0.11.2",
   "description": "A curated library of Claude Code Agent Skills covering the full software lifecycle, with orchestrator-routed activation that scales past the skill-listing budget.",
   "type": "module",
   "bin": {

package/skills/project-documentation/SKILL.md

@@ -22,6 +22,9 @@ Identify which documents the project needs based on context:
 | Inline docs (JSDoc/docstrings) | Public APIs, complex logic | Developers reading the code |
 
 Ask the user which they need. If unsure, start with README — every project needs one.
+Every document must answer a question someone actually has, so for each new one
+you propose or are asked for, **ask the user who reads it and what question it
+answers for them**, next to your draft or plan rather than in place of it.
 
 Two modes use this skill. **Authoring** creates a document that doesn't exist yet
 (the four workflows below). **Sync** reconciles documents that already exist
@@ -222,7 +225,7 @@ For code-level documentation (JSDoc, Python docstrings, Go doc comments):
 
 - **KISS**: Write the minimum documentation that makes the project usable. Don't over-document internals.
 - **DRY**: Don't duplicate information across docs. Link between documents instead.
-- **YAGNI**: Don't write architecture docs for a 200-line script. Match documentation depth to project complexity. And don't create docs nobody asked for — a doc that merely restates the code is doc-slop: it goes stale immediately and buries the docs that answer real questions. Every document must answer a question someone actually has.
+- **YAGNI**: Don't write architecture docs for a 200-line script. Match documentation depth to project complexity. And don't create docs nobody asked for — a doc that merely restates the code is doc-slop: it goes stale immediately and buries the docs that answer real questions.
 
 ## Cross-Skill References
 

package/skills/research-methodology/references/source-verification.md

@@ -1,8 +1,5 @@
 # Source Verification
 
-Adapted from article-craft's `references/source-verification.md`
-(swestash/article-craft), cut down for research projects.
-
 The rule: **cite only what you opened.**
 
 ## Trust tiers

package/skills/skill-router/evals/evals.json

@@ -9,7 +9,7 @@
         "Identifies that a dedicated skill / chain applies instead of improvising",
         "Places feature-planning in the chain, and leads with architecture-design where a costly-to-reverse decision dominates",
         "Names the relevant downstream skills (architecture-design, data-modeling) as next steps",
-        "References the New Feature golden path chain"
+        "Orders the work as the New Feature golden path does: planning and the costly-to-reverse design decisions before implementation"
       ]
     },
     {

package/skills/technical-debt-review/evals/evals.json

@@ -30,7 +30,7 @@
     {
       "id": 3,
       "prompt": "There's a 20-line pricing function with a bug in it. Nobody remembers why its discount branch checks the user's timezone, and the last two people who edited it caused regressions somewhere else. Can you fix the bug?",
-      "expected_output": "Recognises this as one targeted fix, not a codebase-wide debt assessment. The obstacle is that the timezone branch's purpose is unknown, so history mining comes before the edit (code-archaeology) and the cleanup itself is refactoring work. Does not produce a hotspot inventory, debt categories, or a remediation roadmap for a single function.",
+      "expected_output": "Recognises this as one targeted fix, not a codebase-wide debt assessment: the fix itself is bug-investigating work. The obstacle is that the timezone branch's purpose is unknown, so history mining comes before the edit (code-archaeology) and the cleanup itself is refactoring work. Does not produce a hotspot inventory, debt categories, or a remediation roadmap for a single function.",
       "assertions": [
         "Recognises this is a single targeted fix rather than a codebase-wide debt assessment",
         "Identifies that the unexplained timezone branch must be understood before it is changed, and refers to code-archaeology or equivalent history mining for recovering why it exists",