diff --git a/.agents/README.md b/.agents/README.md index d674170..61bd34e 100644 --- a/.agents/README.md +++ b/.agents/README.md @@ -15,7 +15,7 @@ Welcome to the **Antigravity Edition** of Spec-Kit. This system is architected t In this edition, Spec-Kit commands have been split into two interactive layers: 1. **Workflows (`/command`)**: High-level orchestrations that guide the agent through a series of logical steps. **The easiest way to run a skill is by typing its corresponding workflow command.** -2. **Skills (`@speckit.name`)**: Packaged agentic capabilities. Mentions of a skill give the agent immediate context and autonomous "know-how" to execute the specific toolset associated with that phase. +2. **Skills (`@speckit-name`)**: Packaged agentic capabilities. Mentions of a skill give the agent immediate context and autonomous "know-how" to execute the specific toolset associated with that phase. > **To understand the power of Skills in Antigravity, read the docs here:** > [https://antigravity.google/docs/skills](https://antigravity.google/docs/skills) @@ -38,15 +38,15 @@ Some skills and scripts reference a `.specify/` directory for templates and proj ```text .specify/ ├── templates/ -│ ├── spec-template.md # Template for /speckit.specify -│ ├── plan-template.md # Template for /speckit.plan -│ ├── tasks-template.md # Template for /speckit.tasks +│ ├── spec-template.md # Template for /speckit-specify +│ ├── plan-template.md # Template for /speckit-plan +│ ├── tasks-template.md # Template for /speckit-tasks │ └── agent-file-template.md # Template for update-agent-context.sh └── memory/ - └── constitution.md # Project governance rules (/speckit.constitution) + └── constitution.md # Project governance rules (/speckit-constitution) ``` -> **Note:** If `.specify/` is absent, skills will still function — they'll create blank files instead of using templates. The constitution workflow (`/speckit.constitution`) will create this structure for you on first run. +> **Note:** If `.specify/` is absent, skills will still function — they'll create blank files instead of using templates. The constitution workflow (`/speckit-constitution`) will create this structure for you on first run. --- @@ -59,34 +59,34 @@ The toolkit is organized into modular components that provide both the logic (Sc ├── skills/ # @ Mentions (Agent Intelligence) │ ├── nestjs-best-practices/ # NestJS Architecture Patterns │ ├── next-best-practices/ # Next.js App Router Patterns -│ ├── speckit.analyze/ # Consistency Checker -│ ├── speckit.checker/ # Static Analysis Aggregator -│ ├── speckit.checklist/ # Requirements Validator -│ ├── speckit.clarify/ # Ambiguity Resolver -│ ├── speckit.constitution/ # Governance Manager -│ ├── speckit.diff/ # Artifact Comparator -│ ├── speckit.implement/ # Code Builder (Anti-Regression) -│ ├── speckit.migrate/ # Legacy Code Migrator -│ ├── speckit.plan/ # Technical Planner -│ ├── speckit.quizme/ # Logic Challenger (Red Team) -│ ├── speckit.reviewer/ # Code Reviewer -│ ├── speckit.security-audit/ # Security Auditor (OWASP/CASL/ClamAV) -│ ├── speckit.specify/ # Feature Definer -│ ├── speckit.status/ # Progress Dashboard -│ ├── speckit.tasks/ # Task Breaker -│ ├── speckit.taskstoissues/ # Issue Tracker Syncer (GitHub + Gitea) -│ ├── speckit.tester/ # Test Runner & Coverage -│ └── speckit.validate/ # Implementation Validator +│ ├── speckit-analyze/ # Consistency Checker +│ ├── speckit-checker/ # Static Analysis Aggregator +│ ├── speckit-checklist/ # Requirements Validator +│ ├── speckit-clarify/ # Ambiguity Resolver +│ ├── speckit-constitution/ # Governance Manager +│ ├── speckit-diff/ # Artifact Comparator +│ ├── speckit-implement/ # Code Builder (Anti-Regression) +│ ├── speckit-migrate/ # Legacy Code Migrator +│ ├── speckit-plan/ # Technical Planner +│ ├── speckit-quizme/ # Logic Challenger (Red Team) +│ ├── speckit-reviewer/ # Code Reviewer +│ ├── speckit-security-audit/ # Security Auditor (OWASP/CASL/ClamAV) +│ ├── speckit-specify/ # Feature Definer +│ ├── speckit-status/ # Progress Dashboard +│ ├── speckit-tasks/ # Task Breaker +│ ├── speckit-taskstoissues/ # Issue Tracker Syncer (GitHub + Gitea) +│ ├── speckit-tester/ # Test Runner & Coverage +│ └── speckit-validate/ # Implementation Validator │ ├── workflows/ # / Slash Commands (Orchestration) -│ ├── 00-speckit.all.md # Full Pipeline (10 steps: Specify → Validate) -│ ├── 01–11-speckit.*.md # Individual phase workflows -│ ├── speckit.prepare.md # Prep Pipeline (5 steps: Specify → Analyze) +│ ├── 00-speckit-all.md # Full Pipeline (10 steps: Specify → Validate) +│ ├── 01–11-speckit-*.md # Individual phase workflows +│ ├── speckit-prepare.md # Prep Pipeline (5 steps: Specify → Analyze) │ ├── schema-change.md # DB Schema Change (ADR-009) │ ├── create-backend-module.md # NestJS Module Scaffolding │ ├── create-frontend-page.md # Next.js Page Scaffolding │ ├── deploy.md # Deployment via Gitea CI/CD -│ └── util-speckit.*.md # Utilities (checklist, diff, migrate, etc.) +│ └── util-speckit-*.md # Utilities (checklist, diff, migrate, etc.) │ └── scripts/ ├── bash/ # Bash Core (Kinetic logic) @@ -112,27 +112,27 @@ The toolkit is organized into modular components that provide both the logic (Sc | Phase | Workflow Trigger | Antigravity Skill | Role | | :---------------- | :---------------------------- | :------------------------ | :------------------------------------------------------ | -| **Full Pipeline** | `/00-speckit.all` | N/A | Runs full SDLC pipeline (10 steps: Specify → Validate). | -| **Governance** | `/01-speckit.constitution` | `@speckit.constitution` | Establishes project rules & principles. | -| **Definition** | `/02-speckit.specify` | `@speckit.specify` | Drafts structured `spec.md`. | -| **Ambiguity** | `/03-speckit.clarify` | `@speckit.clarify` | Resolves gaps post-spec. | -| **Architecture** | `/04-speckit.plan` | `@speckit.plan` | Generates technical `plan.md`. | -| **Decomposition** | `/05-speckit.tasks` | `@speckit.tasks` | Breaks plans into atomic tasks. | -| **Consistency** | `/06-speckit.analyze` | `@speckit.analyze` | Cross-checks Spec vs Plan vs Tasks. | -| **Execution** | `/07-speckit.implement` | `@speckit.implement` | Builds implementation with safety protocols. | -| **Quality** | `/08-speckit.checker` | `@speckit.checker` | Runs static analysis (Linting, Security, Types). | -| **Testing** | `/09-speckit.tester` | `@speckit.tester` | Runs test suite & reports coverage. | -| **Review** | `/10-speckit.reviewer` | `@speckit.reviewer` | Performs code review (Logic, Perf, Style). | -| **Validation** | `/11-speckit.validate` | `@speckit.validate` | Verifies implementation matches Spec requirements. | -| **Preparation** | `/speckit.prepare` | N/A | Runs Specify → Analyze prep sequence (5 steps). | +| **Full Pipeline** | `/00-speckit-all` | N/A | Runs full SDLC pipeline (10 steps: Specify → Validate). | +| **Governance** | `/01-speckit-constitution` | `@speckit-constitution` | Establishes project rules & principles. | +| **Definition** | `/02-speckit-specify` | `@speckit-specify` | Drafts structured `spec.md`. | +| **Ambiguity** | `/03-speckit-clarify` | `@speckit-clarify` | Resolves gaps post-spec. | +| **Architecture** | `/04-speckit-plan` | `@speckit-plan` | Generates technical `plan.md`. | +| **Decomposition** | `/05-speckit-tasks` | `@speckit-tasks` | Breaks plans into atomic tasks. | +| **Consistency** | `/06-speckit-analyze` | `@speckit-analyze` | Cross-checks Spec vs Plan vs Tasks. | +| **Execution** | `/07-speckit-implement` | `@speckit-implement` | Builds implementation with safety protocols. | +| **Quality** | `/08-speckit-checker` | `@speckit-checker` | Runs static analysis (Linting, Security, Types). | +| **Testing** | `/09-speckit-tester` | `@speckit-tester` | Runs test suite & reports coverage. | +| **Review** | `/10-speckit-reviewer` | `@speckit-reviewer` | Performs code review (Logic, Perf, Style). | +| **Validation** | `/11-speckit-validate` | `@speckit-validate` | Verifies implementation matches Spec requirements. | +| **Preparation** | `/speckit-prepare` | N/A | Runs Specify → Analyze prep sequence (5 steps). | | **Schema** | `/schema-change` | N/A | DB schema changes per ADR-009 (no migrations). | -| **Security** | N/A | `@speckit.security-audit` | OWASP Top 10 + CASL + ClamAV audit. | -| **Checklist** | `/util-speckit.checklist` | `@speckit.checklist` | Generates feature checklists. | -| **Diff** | `/util-speckit.diff` | `@speckit.diff` | Compares artifact versions. | -| **Migration** | `/util-speckit.migrate` | `@speckit.migrate` | Port existing code to Spec-Kit. | -| **Red Team** | `/util-speckit.quizme` | `@speckit.quizme` | Challenges logical flaws. | -| **Status** | `/util-speckit.status` | `@speckit.status` | Shows feature completion status. | -| **Tracking** | `/util-speckit.taskstoissues` | `@speckit.taskstoissues` | Syncs tasks to GitHub/Gitea issues. | +| **Security** | N/A | `@speckit-security-audit` | OWASP Top 10 + CASL + ClamAV audit. | +| **Checklist** | `/util-speckit-checklist` | `@speckit-checklist` | Generates feature checklists. | +| **Diff** | `/util-speckit-diff` | `@speckit-diff` | Compares artifact versions. | +| **Migration** | `/util-speckit-migrate` | `@speckit-migrate` | Port existing code to Spec-Kit. | +| **Red Team** | `/util-speckit-quizme` | `@speckit-quizme` | Challenges logical flaws. | +| **Status** | `/util-speckit-status` | `@speckit-status` | Shows feature completion status. | +| **Tracking** | `/util-speckit-taskstoissues` | `@speckit-taskstoissues` | Syncs tasks to GitHub/Gitea issues. | --- @@ -142,14 +142,14 @@ The following skills are designed to work together as a comprehensive defense ag | Step | Skill | Core Question | Focus | | :-------------- | :------------------ | :-------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------- | -| **1. Checker** | `@speckit.checker` | _"Is the code compliant?"_ | **Syntax & Security**. Runs compilation, linting (ESLint/GolangCI), and vulnerability scans (npm audit/govulncheck). Catches low-level errors first. | -| **2. Tester** | `@speckit.tester` | _"Does it work?"_ | **Functionality**. Executes your test suite (Jest/Pytest/Go Test) to ensure logic performs as expected and tests pass. | -| **3. Reviewer** | `@speckit.reviewer` | _"Is the code written well?"_ | **Quality & Maintainability**. Analyzes code structure for complexity, performance bottlenecks, and best practices, acting as a senior peer reviewer. | -| **4. Validate** | `@speckit.validate` | _"Did we build the right thing?"_ | **Requirements**. Semantically compares the implementation against the defined `spec.md` and `plan.md` to ensure all feature requirements are met. | +| **1. Checker** | `@speckit-checker` | _"Is the code compliant?"_ | **Syntax & Security**. Runs compilation, linting (ESLint/GolangCI), and vulnerability scans (npm audit/govulncheck). Catches low-level errors first. | +| **2. Tester** | `@speckit-tester` | _"Does it work?"_ | **Functionality**. Executes your test suite (Jest/Pytest/Go Test) to ensure logic performs as expected and tests pass. | +| **3. Reviewer** | `@speckit-reviewer` | _"Is the code written well?"_ | **Quality & Maintainability**. Analyzes code structure for complexity, performance bottlenecks, and best practices, acting as a senior peer reviewer. | +| **4. Validate** | `@speckit-validate` | _"Did we build the right thing?"_ | **Requirements**. Semantically compares the implementation against the defined `spec.md` and `plan.md` to ensure all feature requirements are met. | > **🤖 Power User Tip:** You can amplify this pipeline by creating a custom **MCP Server** or subagent that delegates heavy reasoning to a dedicated LLM. > -> - **Use Case:** Bind the `@speckit.validate` and `@speckit.reviewer` steps to a large-context model. +> - **Use Case:** Bind the `@speckit-validate` and `@speckit-reviewer` steps to a large-context model. > - **Benefit:** Large-context models (1M+ tokens) excel at analyzing the full project context against the Spec, finding subtle logical flaws that smaller models miss. > - **How:** Create a wrapper script `scripts/gemini-reviewer.sh` that pipes the `tasks.md` and codebase to an LLM, then expose this as a tool. @@ -161,28 +161,28 @@ These workflows function as the "Control Plane" of the project, managing everyth | Step | Workflow | Core Question | Focus | | :----------------- | :-------------------------------------------------- | :-------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **1. Preparation** | `/speckit.prepare` | _"Are we ready?"_ | **The Macro-Workflow**. Runs Skills 02–06 (Specify $\to$ Clarify $\to$ Plan $\to$ Tasks $\to$ Analyze) in one sequence to go from "Idea" to "Ready to Code". | -| **2. Migration** | `/util-speckit.migrate` | _"Can we import?"_ | **Onboarding**. Reverse-engineers existing code into `spec.md`, `plan.md`, and `tasks.md`. | -| **3. Red Team** | `/util-speckit.quizme` | _"What did we miss?"_ | **Hardening**. Socratic questioning to find logical gaps in your specification before you plan. | -| **4. Export** | `/util-speckit.taskstoissues` | _"Who does what?"_ | **Handoff**. Converts your `tasks.md` into GitHub or Gitea issues with labels and milestones. | -| **5. Status** | `/util-speckit.status` | _"Are we there yet?"_ | **Tracking**. Scans all artifacts to report feature completion percentage. | -| **6. Utilities** | `/util-speckit.diff`
`/util-speckit.checklist` | _"What changed?"_ | **Support**. View artifact diffs or generate quick acceptance checklists. | +| **1. Preparation** | `/speckit-prepare` | _"Are we ready?"_ | **The Macro-Workflow**. Runs Skills 02–06 (Specify $\to$ Clarify $\to$ Plan $\to$ Tasks $\to$ Analyze) in one sequence to go from "Idea" to "Ready to Code". | +| **2. Migration** | `/util-speckit-migrate` | _"Can we import?"_ | **Onboarding**. Reverse-engineers existing code into `spec.md`, `plan.md`, and `tasks.md`. | +| **3. Red Team** | `/util-speckit-quizme` | _"What did we miss?"_ | **Hardening**. Socratic questioning to find logical gaps in your specification before you plan. | +| **4. Export** | `/util-speckit-taskstoissues` | _"Who does what?"_ | **Handoff**. Converts your `tasks.md` into GitHub or Gitea issues with labels and milestones. | +| **5. Status** | `/util-speckit-status` | _"Are we there yet?"_ | **Tracking**. Scans all artifacts to report feature completion percentage. | +| **6. Utilities** | `/util-speckit-diff`
`/util-speckit-checklist` | _"What changed?"_ | **Support**. View artifact diffs or generate quick acceptance checklists. | ### 🔄 The Design Sequence **Stage 1: Inception** -- _Legacy Project?_ $\to$ Run **`/util-speckit.migrate`**. -- _New Feature?_ $\to$ Run **`/speckit.prepare`**. +- _Legacy Project?_ $\to$ Run **`/util-speckit-migrate`**. +- _New Feature?_ $\to$ Run **`/speckit-prepare`**. **Stage 2: Hardening** -- Run **`/util-speckit.quizme`** to catch edge cases. -- Run **`/speckit.prepare`** again to regenerate the Plan based on restricted specs. +- Run **`/util-speckit-quizme`** to catch edge cases. +- Run **`/speckit-prepare`** again to regenerate the Plan based on restricted specs. **Stage 3: Handoff** -- Run **`/util-speckit.taskstoissues`** to sync with your board. +- Run **`/util-speckit-taskstoissues`** to sync with your board. --- @@ -192,17 +192,17 @@ Once the `.agents` folder is present, you can talk to your agent as a partner. Y **Example Conversation:** -> **Developer**: "**/02-speckit.specify** Add a real-time notification system using WebSockets." +> **Developer**: "**/02-speckit-specify** Add a real-time notification system using WebSockets." > -> **Antigravity**: "Understood. Executing the **@speckit.specify** skill. Creating feature branch `005-notifications` and drafting the initial specification..." +> **Antigravity**: "Understood. Executing the **@speckit-specify** skill. Creating feature branch `005-notifications` and drafting the initial specification..." > _(Antigravity creates branch, drafts spec.md)_ > -> **Antigravity**: "Specification ready. I've identified some ambiguity in the reconnection strategy. Should I use **@speckit.clarify** to resolve this?" +> **Antigravity**: "Specification ready. I've identified some ambiguity in the reconnection strategy. Should I use **@speckit-clarify** to resolve this?" > -> **Developer**: "Yes, use **@speckit.clarify**." +> **Developer**: "Yes, use **@speckit-clarify**." > _(Antigravity executes the skill logic, interviewing the developer and updating the spec)_ > -> **Antigravity**: "The spec is now robust. I'm ready to trigger **/04-speckit.plan** and **/05-speckit.tasks** to prepare for implementation." +> **Antigravity**: "The spec is now robust. I'm ready to trigger **/04-speckit-plan** and **/05-speckit-tasks** to prepare for implementation." --- @@ -212,7 +212,7 @@ To get the most out of this system, follow these **Spec-Driven Development (SDD) ### 1. The Constitution is King 👑 -**Never skip `/01-speckit.constitution`.** +**Never skip `/01-speckit-constitution`.** - This file is the "Context Window Anchor" for the AI. - It prevents hallucinations about tech stack (e.g., "Don't use jQuery" or "Always use TypeScript strict mode"). @@ -222,9 +222,9 @@ To get the most out of this system, follow these **Spec-Driven Development (SDD) Don't rush to code. The workflow exists to catch errors _cheaply_ before they become expensive bugs. -- **Ambiguity Layer**: `/03-speckit.clarify` catches misunderstandings. -- **Logic Layer**: `/util-speckit.quizme` catches edge cases. -- **Consistency Layer**: `/06-speckit.analyze` catches gaps between Spec and Plan. +- **Ambiguity Layer**: `/03-speckit-clarify` catches misunderstandings. +- **Logic Layer**: `/util-speckit-quizme` catches edge cases. +- **Consistency Layer**: `/06-speckit-analyze` catches gaps between Spec and Plan. ### 3. The 15-Minute Rule ⏱️ @@ -240,17 +240,17 @@ If you change your mind mid-project: 1. Don't just edit the code. 2. Edit the `spec.md` to reflect the new requirement. -3. Run `/util-speckit.diff` to see the drift. +3. Run `/util-speckit-diff` to see the drift. 4. This keeps your documentation alive and truthful. --- ## 🧩 Adaptation Notes -- **Skill-Based Autonomy**: Mentions like `@speckit.plan` trigger the agent's internalized understanding of how to perform that role. +- **Skill-Based Autonomy**: Mentions like `@speckit-plan` trigger the agent's internalized understanding of how to perform that role. - **Shared Script Core**: Logic resides in `.agents/scripts/bash` (modular) with PowerShell equivalents in `scripts/powershell/` for Windows-native execution. - **Agent-Native**: Designed to be invoked via Antigravity tool calls and reasoning rather than just terminal strings. -- **LCBP3-DMS Specific**: Includes project-specific skills (`nestjs-best-practices`, `next-best-practices`, `speckit.security-audit`) and workflows (`/schema-change`, `/create-backend-module`, `/deploy`). +- **LCBP3-DMS Specific**: Includes project-specific skills (`nestjs-best-practices`, `next-best-practices`, `speckit-security-audit`) and workflows (`/schema-change`, `/create-backend-module`, `/deploy`). --- @@ -287,8 +287,8 @@ If you change your mind mid-project: | Create Frontend Page | `/create-frontend-page` | Next.js App Router page | | Schema Change | `/schema-change` | ADR-009: No migrations | | Deploy | `/deploy` | Blue-Green via Gitea CI/CD | -| UAT Feature Check | `/11-speckit.validate` | vs `01-05-acceptance-criteria.md` | -| Security Audit | `@speckit.security-audit` | OWASP + CASL + ClamAV | +| UAT Feature Check | `/11-speckit-validate` | vs `01-05-acceptance-criteria.md` | +| Security Audit | `@speckit-security-audit` | OWASP + CASL + ClamAV | ### 🚫 Critical Forbidden Actions diff --git a/.agents/skills/speckit.analyze/SKILL.md b/.agents/skills/speckit-analyze/SKILL.md similarity index 96% rename from .agents/skills/speckit.analyze/SKILL.md rename to .agents/skills/speckit-analyze/SKILL.md index 0a3b64c..3b558d0 100644 --- a/.agents/skills/speckit.analyze/SKILL.md +++ b/.agents/skills/speckit-analyze/SKILL.md @@ -1,9 +1,9 @@ --- -name: speckit.analyze +name: speckit-analyze description: Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation. version: 1.0.0 depends-on: - - speckit.tasks + - speckit-tasks --- ## User Input @@ -21,13 +21,13 @@ You are the **Antigravity Consistency Analyst**. Your role is to identify incons ## Task ### Goal -Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `/speckit.tasks` has successfully produced a complete `tasks.md`. +Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `/speckit-tasks` has successfully produced a complete `tasks.md`. ## Operating Constraints **STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually). -**Constitution Authority**: The project constitution (`.specify/memory/constitution.md`) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside `/speckit.analyze`. +**Constitution Authority**: The project constitution (`.specify/memory/constitution.md`) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside `/speckit-analyze`. ### Steps @@ -163,9 +163,9 @@ Output a Markdown report (no file writes) with the following structure: At end of report, output a concise Next Actions block: -- If CRITICAL issues exist: Recommend resolving before `/speckit.implement` +- If CRITICAL issues exist: Recommend resolving before `/speckit-implement` - If only LOW/MEDIUM: User may proceed, but provide improvement suggestions -- Provide explicit command suggestions: e.g., "Run /speckit.specify with refinement", "Run /speckit.plan to adjust architecture", "Manually edit tasks.md to add coverage for 'performance-metrics'" +- Provide explicit command suggestions: e.g., "Run /speckit-specify with refinement", "Run /speckit-plan to adjust architecture", "Manually edit tasks.md to add coverage for 'performance-metrics'" ### 8. Offer Remediation diff --git a/.agents/skills/speckit.checker/SKILL.md b/.agents/skills/speckit-checker/SKILL.md similarity index 99% rename from .agents/skills/speckit.checker/SKILL.md rename to .agents/skills/speckit-checker/SKILL.md index efec13a..47e59e5 100644 --- a/.agents/skills/speckit.checker/SKILL.md +++ b/.agents/skills/speckit-checker/SKILL.md @@ -1,5 +1,5 @@ --- -name: speckit.checker +name: speckit-checker description: Run static analysis tools and aggregate results. version: 1.0.0 depends-on: [] diff --git a/.agents/skills/speckit.checklist/SKILL.md b/.agents/skills/speckit-checklist/SKILL.md similarity index 99% rename from .agents/skills/speckit.checklist/SKILL.md rename to .agents/skills/speckit-checklist/SKILL.md index 0886f34..f6674d8 100644 --- a/.agents/skills/speckit.checklist/SKILL.md +++ b/.agents/skills/speckit-checklist/SKILL.md @@ -1,5 +1,5 @@ --- -name: speckit.checklist +name: speckit-checklist description: Generate a custom checklist for the current feature based on user requirements. version: 1.0.0 --- @@ -101,7 +101,7 @@ You are the **Antigravity Quality Gatekeeper**. Your role is to validate the qua - Format: `[domain].md` - If file exists, append to existing file - Number items sequentially starting from CHK001 - - Each `/speckit.checklist` run creates a NEW file (never overwrites existing checklists) + - Each `/speckit-checklist` run creates a NEW file (never overwrites existing checklists) **CORE PRINCIPLE - Test the Requirements, Not the Implementation**: Every checklist item MUST evaluate the REQUIREMENTS THEMSELVES for: @@ -219,7 +219,7 @@ You are the **Antigravity Quality Gatekeeper**. Your role is to validate the qua - Actor/timing - Any explicit user-specified must-have items incorporated -**Important**: Each `/speckit.checklist` command invocation creates a checklist file using short, descriptive names unless file already exists. This allows: +**Important**: Each `/speckit-checklist` command invocation creates a checklist file using short, descriptive names unless file already exists. This allows: - Multiple checklists of different types (e.g., `ux.md`, `test.md`, `security.md`) - Simple, memorable filenames that indicate checklist purpose diff --git a/.agents/skills/speckit.checklist/templates/checklist-template.md b/.agents/skills/speckit-checklist/templates/checklist-template.md similarity index 90% rename from .agents/skills/speckit.checklist/templates/checklist-template.md rename to .agents/skills/speckit-checklist/templates/checklist-template.md index 806657d..c4aa166 100644 --- a/.agents/skills/speckit.checklist/templates/checklist-template.md +++ b/.agents/skills/speckit-checklist/templates/checklist-template.md @@ -4,13 +4,13 @@ **Created**: [DATE] **Feature**: [Link to spec.md or relevant documentation] -**Note**: This checklist is generated by the `/speckit.checklist` command based on feature context and requirements. +**Note**: This checklist is generated by the `/speckit-checklist` command based on feature context and requirements.