@antoneeo/agentic-sdlc-skill 1.0.9 → 1.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +5 -0
  2. package/gemini-extension.json +1 -1
  3. package/package.json +1 -1
  4. package/scripts/init.js +4 -4
package/CHANGELOG.md CHANGED
@@ -2,6 +2,11 @@
2
2
 
3
3
  Tutte le modifiche significative a questa skill saranno documentate in questo file.
4
4
 
5
+ ## [1.1.0] - 2026-05-10
6
+ ### Fixed
7
+ - Fixed path inconsistencies in the generated `CLAUDE.md`, `GEMINI.md`, and `.cursorrules` protocols. Added full paths (`ai_docs/strategic/`) to all document references to ensure AI agents (like Claude) can correctly find and update them.
8
+ - Cleaned up encoding issues in initialization scripts.
9
+
5
10
  ## [1.0.9] - 2026-05-10
6
11
  ### Added
7
12
  - New **Smart Discovery** system during project initialization.
package/gemini-extension.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agentic-sdlc-skill",
3
- "version": "1.0.9",
3
+ "version": "1.1.0",
4
4
  "description": "Protocollo SDLC Documentation-First per Gemini CLI.",
5
5
  "author": "Antonio Pinto (https://github.com/Antoneeo)"
6
6
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@antoneeo/agentic-sdlc-skill",
3
- "version": "1.0.9",
3
+ "version": "1.1.0",
4
4
  "description": "Protocollo SDLC Documentation-First per Gemini CLI. Gestisce audit, analisi, sviluppo e chiusura feature con documentazione sincronizzata.",
5
5
  "keywords": [
6
6
  "gemini-cli",
package/scripts/init.js CHANGED
@@ -54,19 +54,19 @@ Before responding to any operational request:
54
54
  ## 2. Request Analysis Phase
55
55
  For every new feature request:
56
56
  - Create \`ai_docs/solutions/ANALYSIS_[feature_name].md\` (Objective, Impact, Action Plan, Test Strategy).
57
- - Add a entry in \`features_history.md\` with status \`[PLANNED]\`.
57
+ - Add an entry in \`ai_docs/strategic/features_history.md\` with status \`[PLANNED]\`.
58
58
 
59
59
  ## 3. Development and Testing Phase
60
60
  Only after Phase 2 is complete:
61
- 1. Update feature status to \`[IN_PROGRESS]\`.
61
+ 1. Update feature status to \`[IN_PROGRESS]\` in \`ai_docs/strategic/features_history.md\`.
62
62
  2. Implement code surgically following the plan.
63
63
  3. **Mandatory:** Write automated tests following the **AAA (Arrange, Act, Assert)** pattern.
64
64
  4. Execute tests. If they fail, fix and re-run until Exit Code is 0.
65
65
 
66
66
  ## 4. Closing Phase
67
67
  Upon feature completion:
68
- - Update \`architecture.md\` and \`existing_features.md\` if necessary.
69
- - Update \`features_history.md\` setting status to \`[COMPLETED]\`.
68
+ - Update \`ai_docs/strategic/architecture.md\` and \`ai_docs/strategic/existing_features.md\` if necessary.
69
+ - Update \`ai_docs/strategic/features_history.md\` setting status to \`[COMPLETED]\`.
70
70
  `;
71
71
 
72
72
  const codexHooksContent = JSON.stringify({