akili-specs 2.7.0 → 2.7.1

package/.claude/commands/akili-archive.md

@@ -1,5 +1,8 @@
 ---
 description: Archive a completed spec task, run the Kaizen retrospective, sync agent guides and CodeGraph, and keep the TRD current.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Archive AKILI-SPECS Spec
@@ -174,3 +177,9 @@ Present:
 - Do not delete spec folders as part of archiving; only move them into `docs/specs/archive/`.
 - The Kaizen retrospective must never block the archive. If retrospective inputs are missing or the user declines, append a metrics-only (or clean-run) entry to `docs/specs/kaizen-log.md` and continue to Step 5.
 - Never edit files outside `docs/specs/kaizen-log.md` without explicit user approval in Step 4.3.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-audit.md

@@ -1,5 +1,8 @@
 ---
 description: Run spec-to-code drift auditing to detect differences between active codebase reality and the active UX/UI design and TRD.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Audit AKILI Specifications for Drift
@@ -95,3 +98,9 @@ Summarize the conformance score, key discrepancies found, and recommended remedi
 1. Fix documented specs (update baseline docs in place).
 2. Schedule task specs to implement missing functionality in the code.
 3. Keep the report for review.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-constitution.md

@@ -1,5 +1,8 @@
 ---
 description: Establish or strengthen the project-wide AKILI-SPECS foundation and baseline docs (PRD, UX/UI Design, TRD).
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Establish AKILI-SPECS Constitution
@@ -418,3 +421,9 @@ Ask the user whether to approve or request changes. If changes are requested, re
 ## Outcome
 
 At the end of `/akili-constitution`, the repository should have a project-level baseline that future `/akili-specify`, `/akili-execute`, `/akili-validate`, and `/akili-test` work can rely on without guessing the structure or conventions. The `.agents/` personas must be in place so that `/akili-execute` can run the Leader → Implementer → Reviewer rework loop and `/akili-test` can run the Leader → Tester(s) harness without falling back to inline personas. The root guides must also carry a `## Model Routing` registry (Step 8C) so each phase runs on a model matched to its demand, with the Reviewer on a different model than the Implementer.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-execute.md

@@ -1,5 +1,8 @@
 ---
 description: Execute approved specs systematically following the AKILI-SPECS methodology with spec-to-code traceability.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Execute AKILI-SPECS Tasks
@@ -240,3 +243,9 @@ A minimal PASS-on-first-attempt entry can be compact; a HALT or rework entry mus
   2. Document the blocker, alternatives, and revised technical direction in `execution.md` inside a new `## Pivot Record: <Task ID>` section.
   3. Modify the spec's `requirements.md`, `design.md`, and/or `tasks.md` to map out the updated plan.
   4. Stop, explain the situation to the user, and obtain explicit review/approval on the pivot before resuming execution.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-propose.md

@@ -1,5 +1,8 @@
 ---
 description: Propose new features or changes by initiating a new detailed technical spec process.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Propose AKILI-SPECS Change
@@ -251,3 +254,9 @@ Generate a short, easy-to-understand summary (summary facil de entender de lo qu
 7. next command to run after approval (matched to the type)
 
 Ask whether to approve the proposal, revise it, or stop.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-quick.md

@@ -1,5 +1,8 @@
 ---
 description: Fast-track a trivial, low-risk change (copy edit, color tweak, small style/text change) with minimal traceability and automatic escalation when it is not actually trivial.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Fast-Track a Trivial AKILI-SPECS Change
@@ -123,3 +126,9 @@ Generate a short, easy-to-understand summary (summary facil de entender de lo qu
 - One change per invocation. Batch unrelated tweaks into separate `/akili-quick` runs or a proper spec.
 - When in doubt about triviality, escalate. A wrongly fast-tracked change costs more than a Lite spec.
 - Keep the edit and the context minimal — this command's whole value is speed and low token cost.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-resume.md

@@ -1,5 +1,8 @@
 ---
 description: Resume work after a session break by scanning active specs and presenting a multi-spec dashboard briefing.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Resume AKILI-SPECS Session
@@ -124,3 +127,9 @@ No files are created or modified. The command outputs a screen summary only.
 - If `docs/specs/` does not exist, report that the project has no active specs and suggest running `/akili-constitution` or `/akili-propose`.
 - If `docs/specs/` is empty (only `archive/` exists), report that all specs are archived and suggest running `/akili-propose` for new work.
 - If a spec folder exists but has no readable files, report it as an incomplete spec and suggest running `/akili-specify <spec-path>`.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-seo.md

@@ -1,5 +1,8 @@
 ---
 description: Enhance pages and search engine optimization following SEO best practices.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # SEO Setup & Audit via Google Search Console
@@ -275,3 +278,9 @@ After the command completes, verify:
 - If `search_analytics_query` returns no rows for a newly verified property, this is expected. Do not mark as failure.
 - If the Indexing API is suggested as a fix, decline it for non-`JobPosting`/`BroadcastEvent` content and explain why.
 - If a skill is unavailable, fall back to the next documented skill and note it in the report.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-specify.md

@@ -1,5 +1,8 @@
 ---
 description: Draft detailed requirements, UI/UX designs, and technical tasks for a proposed feature.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Generate AKILI-SPECS for Module
@@ -334,3 +337,9 @@ When the spec is ready, generate a short, easy-to-understand summary (summary fa
 7. Open questions or assumptions that still need user confirmation
 
 If a proposal existed, mention whether the generated spec stayed aligned with it or changed based on implementation discovery.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-test.md

@@ -1,5 +1,8 @@
 ---
 description: Write and execute comprehensive automated unit/integration tests for the implemented feature.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Test AKILI-SPECS Implementation
@@ -174,3 +177,9 @@ If `ui-ux-pro-max` is unavailable, use `frontend-design` plus the UX/UI design d
 - If no automated test is practical, document the manual verification steps and why automation was deferred.
 - A Tester must never rewrite a test to hide a genuine product defect; a real failure is reported as `PRODUCT_BUG`, not silenced.
 - Do not delegate trivial single-test work to a subagent when running it inline is cheaper (see the Deployment Rule).
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/commands/akili-validate.md

@@ -1,5 +1,8 @@
 ---
 description: Validate that the implemented feature strictly matches all requirements, design tokens, and user flows.
+license: MIT
+metadata:
+  author: Juan Carlos Cadavid (jcadavid.com)
 ---
 
 # Validate AKILI-SPECS Implementation
@@ -184,3 +187,9 @@ The work is ready to consider complete when:
 - tests cover the key requirements and scenarios
 - implementation drift is reflected in the AKILI-SPECS docs or execution notes
 - the user has reviewed the validation summary
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/templates/implementer.md

@@ -34,3 +34,9 @@ When you finish implementing and verifying your task, provide a concise response
 1.  **Task Completed:** (Brief 1-sentence summary of what you implemented)
 2.  **Verification Command Run:** (e.g. `npm run test` or `vitest run`)
 3.  **Verification Output/Evidence:** (Paste passing test outputs or compile success logs)
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/templates/leader.md

@@ -75,3 +75,9 @@ After each task completes (whether on first pass or after self-correction), repo
 6. **Next step:** the next eligible task and a prompt to continue, pause, or skip.
 
 Keep this report concise. The full audit trail belongs in `execution.md`, not in chat.
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/templates/reviewer.md

@@ -51,3 +51,9 @@ Use this ONLY if you detect a critical architectural violation, the introduction
 STATUS: FATAL_FAIL
 SUMMARY: (Clear explanation of the catastrophic failure and why the loop must be aborted)
 ```
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/.claude/templates/tester.md

@@ -72,3 +72,9 @@ BUG:
 - **Failing Test:** (test file::test name — kept red on purpose)
 - **Observed vs Expected:** (actual behavior vs the required behavior)
 ```
+
+---
+
+## Authorship
+
+AKILI-SPECS methodology by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com). Licensed under the MIT License.

package/CHANGELOG.md

@@ -10,6 +10,14 @@ The format is inspired by Keep a Changelog and the repository follows semantic v
 
 - No unreleased changes yet.
 
+## [2.7.1] - 2026-07-20
+
+### Added
+
+- **Authorship section in commands and templates:** Every command in `.claude/commands/` and every agent role template in `.claude/templates/` now ends with an `## Authorship` section crediting the AKILI-SPECS methodology to Juan Carlos Cadavid ([jcadavid.com](https://jcadavid.com)).
+- **Authorship in README, LICENSE, and package metadata:** The README gains an `## Authorship` section, the MIT LICENSE copyright line uses the full author name and site, and `package.json` declares the `author` field.
+- **License metadata in commands:** Every command in `.claude/commands/` declares `license: MIT` and `metadata.author` in its frontmatter (matching the convention used by community skills), and the `## Authorship` footer of commands and templates states the MIT License. Third-party skills bundled in `.claude/skills/` keep their original authors and licenses untouched.
+- **Community governance files:** `CONTRIBUTING.md` (PR-only workflow, changelog discipline, and security rules for editing agent-executed prompt files), `SECURITY.md` (private vulnerability reporting with prompt-injection and installer threat scope), and `.github/CODEOWNERS` (maintainer review required on every change).
 ## [2.7.0] - 2026-07-20
 
 ### Added

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 Juan Cadavid
+Copyright (c) 2026 Juan Carlos Cadavid (jcadavid.com)
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -832,3 +832,9 @@ and the default registry for Claude Code (PRO) and OpenCode Go.
 - Skills were copied with their bundled references and helper assets.
 - This repository stores the current methodology baseline so it can be reused or versioned independently.
 - Dotfiles are snapshots of the working environment and may include plugin source copies for portability.
+
+## Authorship
+
+The AKILI-SPECS methodology is created and maintained by **Juan Carlos Cadavid** — [jcadavid.com](https://jcadavid.com).
+
+Every command in `.claude/commands/` and every agent role template in `.claude/templates/` carries this authorship notice. The project is released under the [MIT License](LICENSE): you are free to use, modify, and redistribute it, provided the copyright and attribution notices are kept intact.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akili-specs",
-  "version": "2.7.0",
+  "version": "2.7.1",
   "description": "Portable AKILI-SPECS methodology commands and skills for AI-assisted development.",
   "homepage": "https://github.com/JuankCadavid/akili-specs#readme",
   "repository": {
@@ -46,5 +46,6 @@
   "engines": {
     "node": ">=18.0.0"
   },
-  "license": "MIT"
+  "license": "MIT",
+  "author": "Juan Carlos Cadavid (https://jcadavid.com)"
 }