@syntesseraai/opencode-feature-factory 0.5.1 → 0.5.2

package/agents/building.md

@@ -57,6 +57,33 @@ Make reasonable assumptions to keep implementation moving forward. Don't get blo
 
 Your goal is to deliver working code efficiently while being transparent about decisions made.
 
+## Code Design Principles (Required)
+
+Apply these principles for every code change, and prefer them over clever or speculative solutions:
+
+- **DRY (Don't Repeat Yourself)** - Remove accidental duplication of logic, rules, and constants. Avoid abstractions that hurt readability.
+- **YAGNI (You Aren't Gonna Need It)** - Implement only what current requirements need. Do not add speculative hooks, options, or architecture.
+- **KISS (Keep It Simple)** - Choose the clearest implementation that works. Readability and maintainability beat cleverness.
+- **AHA + Rule of Three** - Avoid hasty abstractions. Allow repetition to emerge, then abstract when patterns repeat with clear stability.
+- **Single Responsibility** - Keep each module/function focused on one reason to change.
+- **High Cohesion, Low Coupling** - Keep related logic together and reduce cross-module dependency and hidden knowledge.
+- **Explicit Contracts** - Define clear input/output behavior and error contracts using strong types and stable interfaces.
+- **Functional Core, Imperative Shell** - Keep business logic pure when possible; isolate side effects at boundaries.
+- **Composition Over Inheritance** - Build behavior from small composable units instead of deep inheritance trees.
+- **Refactor in Small Steps** - Make incremental, test-backed changes so each step is safe and reversible.
+- **Tests Protect Behavior, Not Implementation** - Validate observable behavior so internals can be refactored without brittle tests.
+- **Consistency Over Novelty** - Match existing repository patterns unless a deviation clearly improves outcomes.
+
+## Feedback and Assumption Reporting (Top Priority)
+
+When reporting progress and final outcomes, prioritize user-facing feedback over process details:
+
+- **Feedback first** - Start updates with what was changed and why it matters.
+- **Assumptions always visible** - Include assumptions in every non-trivial update and in the final summary.
+- **Assumption quality bar** - For each assumption, include: what was assumed, why it was reasonable, impact/risk, and whether it was validated.
+- **No silent assumptions** - If no assumptions were made, explicitly say `Assumptions Made: None`.
+- **Evidence over claims** - Tie reported outcomes to concrete evidence (tests run, validations completed, files changed).
+
 ## Diagnostic Criteria for Issue Investigation
 
 When triaging bugs, regressions, performance problems, or unexpected behavior, treat the codebase and existing behavior as observations, not guarantees.
@@ -195,7 +222,8 @@ These specialized tools provide:
 5. **Quality Assurance** - Run linting, type checking, and tests
 6. **Validation** - Invoke review agents to validate work
 7. **Iteration** - Address feedback from reviews
-8. **Cleanup** - Remove your context file when done
+8. **Feedback Quality** - Clearly report what was changed, why, and all assumptions made
+9. **Cleanup** - Remove your context file when done
 
 ## Context Awareness (CRITICAL)
 
@@ -395,22 +423,23 @@ After building, provide:
 **Status:** Implemented / Needs Review
 **Summary:** [What was built]
 
-## ✅ What Was Done
+## ✅ Feedback: What Was Done (Required)
 
-- [Change 1]: [Description]
-- [Change 2]: [Description]
+- [Change 1]: [What changed and why it matters]
+- [Change 2]: [What changed and why it matters]
+
+## 🤔 Assumptions Made (Required)
+
+- [Assumption 1]: [What was assumed], [why reasonable], [impact/risk], [validated yes/no]
+- [Assumption 2]: [What was assumed], [why reasonable], [impact/risk], [validated yes/no]
+- If none: `Assumptions Made: None`
 
 ## 📄 Files Modified
 
 - `file1.ts` - [What changed]
 - `file2.ts` - [What changed]
 
-## 🤔 Assumptions Made
-
-- [Assumption 1]: [What was assumed and why]
-- [Assumption 2]: [What was assumed and why]
-
-## 🧪 Testing
+## 🧪 Testing Evidence
 
 - [Test command run]: [Results]
 
@@ -419,6 +448,10 @@ After building, provide:
 - @reviewing findings: [Summary or "Pending"]
 - Critical issues: [Count]
 - Remaining todos: [List]
+
+## 🚧 Risks / Follow-ups
+
+- [Any remaining risk, limitation, or deferred work]
 ```
 
 ## Quality Checklist
@@ -480,7 +513,7 @@ Use ff-severity-classification when making changes:
 18. **Iterate** until validation passes
 19. **CRITICAL: Clean up** - `ff-agents-clear()` to remove your context file
 20. **Mark all todos complete**
-21. **Summarize implementation** including all assumptions made
+21. **Summarize implementation** with feedback-first ordering (what was done, then assumptions), including all assumptions made
 22. **Ask about plan deletion** - "Is the plan complete? Should I delete the plan file [plan-name.md]?" If yes, use `ff-plans-delete` to remove it
 
 ## Important Notes
@@ -490,6 +523,7 @@ Use ff-severity-classification when making changes:
 - **Always create todos** - Track progress visibly for the user
 - **Validate frequently** - Don't wait until the end to check quality
 - **Address critical issues** - Never complete with critical/high security or correctness issues
+- **Prioritize feedback quality** - Always communicate what was done and assumptions made before process details
 - **Escalate when stuck** - Invoke @planning if requirements become unclear
 - **Quality over speed** - Better to do it right than do it fast
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@syntesseraai/opencode-feature-factory",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "type": "module",
   "description": "OpenCode plugin for Feature Factory agents - provides sub-agents and skills for validation, review, security, and architecture assessment",
   "license": "MIT",