From ce809d9eb8b3de1e087a8522330cb85f35b6cd2f Mon Sep 17 00:00:00 2001 From: palucdev Date: Sat, 20 Jun 2026 00:25:46 +0200 Subject: [PATCH] Replace commands references with invocable skills --- AGENTS.md | 2 +- README.md | 54 +++++++++---------- agents/code-quality-pragmatist.md | 2 +- agents/code-reviewer.md | 8 +-- agents/production-readiness-checker.md | 6 +-- agents/project-analyzer.md | 4 +- agents/reality-assessor.md | 2 +- agents/task-classifier.md | 6 +-- docs/{commands.md => skills.md} | 54 +++++++++---------- docs/workflows.md | 38 ++++++------- skills/development/SKILL.md | 10 ++-- skills/docs-manager/SKILL.md | 4 +- .../references/agents-md-template.md | 4 +- skills/flow-init/SKILL.md | 2 +- skills/migration/SKILL.md | 6 +-- skills/performance/SKILL.md | 6 +-- skills/product-design/SKILL.md | 14 ++--- skills/quick-bugfix/SKILL.md | 24 ++++----- skills/quick-dev/SKILL.md | 18 +++---- skills/quick-plan/SKILL.md | 12 ++--- skills/research/SKILL.md | 10 ++-- skills/reviews-code/SKILL.md | 6 +-- skills/reviews-pragmatic/SKILL.md | 6 +-- skills/reviews-production-readiness/SKILL.md | 6 +-- skills/reviews-reality-check/SKILL.md | 6 +-- skills/reviews-spec-audit/SKILL.md | 6 +-- skills/standards-discover/SKILL.md | 16 +++--- skills/standards-update/SKILL.md | 10 ++-- skills/work/SKILL.md | 34 ++++++------ templates/quick-bugfix-task.yml | 2 +- templates/quick-dev-task.yml | 2 +- templates/quick-plan-task.yml | 2 +- 32 files changed, 191 insertions(+), 191 deletions(-) rename docs/{commands.md => skills.md} (88%) diff --git a/AGENTS.md b/AGENTS.md index 7f08250..a7e55b8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -533,7 +533,7 @@ Skills for generating diagrams and rendering markdown content into shareable for ## Available Workflows & Skills -Under the Antigravity CLI, workflows are structured as Skills instead of user-facing slash commands. When a user requests a task, the agent automatically matches it to the appropriate workflow, reads the skill's `SKILL.md` using `view_file`, and executes the corresponding orchestrator. +Under the Antigravity CLI, workflows are structured as Skills. They can be invoked by the user using slash commands in the format `/:` (e.g., `/agyflow:work` or `/agyflow:quick-dev`). When a user requests a task, the agent automatically matches it to the appropriate workflow, reads the skill's `SKILL.md` using `view_file`, and executes the corresponding orchestrator. All orchestrators support resuming from a specific phase via state restoration from `orchestrator-state.yml`. diff --git a/README.md b/README.md index d0b9e9a..ab7297a 100644 --- a/README.md +++ b/README.md @@ -73,7 +73,7 @@ agy plugin uninstall agyflow Initialize your project to auto-detect coding standards and generate project documentation. Run this inside an active `agy` session: ```bash -/flow-init +/agyflow:flow-init ``` This scans your codebase and creates `.agyflow/` with standards, docs, and task folders. May take a few minutes on larger projects. @@ -81,7 +81,7 @@ This scans your codebase and creates `.agyflow/` with standards, docs, and task If you have another project already using Agyflow, you can reuse its standards as a starting point: ```bash -/flow-init --standards-from=/path/to/other-project +/agyflow:flow-init --standards-from=/path/to/other-project ``` ## First Workflow @@ -89,13 +89,13 @@ If you have another project already using Agyflow, you can reuse its standards a Start a workflow by running this inside an active `agy` session: ```bash -/development Add user profile page with avatar upload +/agyflow:development Add user profile page with avatar upload ``` Or just discuss your task with Agent and then run: ```bash -/development +/agyflow:development ``` The plugin picks up context from your conversation - no arguments needed. @@ -110,18 +110,18 @@ The plugin picks up context from your conversation - no arguments needed. All artifacts are saved in `.agyflow/tasks/` organized by type and date. -### Context-Aware Commands +### Context-Aware Skills -Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type: +Every workflow skill works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type: ``` You: "The login page throws a 500 error when the session expires" -You: /development +You: /agyflow:development → Auto-detects: bug fix, extracts description from conversation ``` ``` -You: /standards-update +You: /agyflow:standards-update → Scans conversation for patterns like "we always use..." or "prefer X over Y" ``` @@ -129,27 +129,27 @@ You can always be explicit when you prefer - arguments and flags simply override ## Supported Workflows -| Command | Use When | +| Skill | Use When | | ----------------- | ------------------------------------------- | -| `/development` | Features, bug fixes, enhancements | -| `/research` | Research with synthesis and solution design | -| `/performance` | Optimizing speed or resource usage | -| `/migration` | Changing technologies or patterns | -| `/product-design` | Product and feature design | +| `/agyflow:development` | Features, bug fixes, enhancements | +| `/agyflow:research` | Research with synthesis and solution design | +| `/agyflow:performance` | Optimizing speed or resource usage | +| `/agyflow:migration` | Changing technologies or patterns | +| `/agyflow:product-design` | Product and feature design | -Task type (feature/bug/enhancement) is auto-detected from context. Override with `--type=feature|bug|enhancement` if needed. Or use `/work` as a single entry point that routes to the right workflow. +Task type (feature/bug/enhancement) is auto-detected from context. Override with `--type=feature|bug|enhancement` if needed. Or use `/agyflow:work` as a single entry point that routes to the right workflow. -### Quick Commands +### Quick Skills For smaller tasks that don't need a full workflow: -| Command | Use When | Artifacts | +| Skill | Use When | Artifacts | | --------------- | ----------------------------------------------------------- | --------------------------------------- | -| `/quick-plan` | You want a plan with standards awareness before coding | `task.yml`, `findings.md` | -| `/quick-dev` | You know what to do - just implement with standards applied | `task.yml`, `summary.md` | -| `/quick-bugfix` | Quick TDD-driven bug fix — write failing test, fix, verify | `task.yml`, `findings.md`, `summary.md` | +| `/agyflow:quick-plan` | You want a plan with standards awareness before coding | `task.yml`, `findings.md` | +| `/agyflow:quick-dev` | You know what to do - just implement with standards applied | `task.yml`, `summary.md` | +| `/agyflow:quick-bugfix` | Quick TDD-driven bug fix — write failing test, fix, verify | `task.yml`, `findings.md`, `summary.md` | -All quick commands create lightweight task directories under `.agyflow/tasks/quick-{type}/` with a `task.yml` for traceability. +All quick skills create lightweight task directories under `.agyflow/tasks/quick-{type}/` with a `task.yml` for traceability. ## Standards-Aware Development @@ -157,8 +157,8 @@ This is the key differentiator. Agyflow doesn't just run workflows - it learns y - **`flow-init`** scans config files, source code, and documentation to auto-detect your coding standards - **Continuous checking** - standards are consulted before specification, during planning, and while coding (not just at the start) -- **`/standards-discover`** refreshes standards from your evolving codebase -- **`/standards-update`** lets you add or refine standards manually, or sync from another project with `--from=PATH` +- **`/agyflow:standards-discover`** refreshes standards from your evolving codebase +- **`/agyflow:standards-update`** lets you add or refine standards manually, or sync from another project with `--from=PATH` Standards live in `.agyflow/docs/standards/` and are indexed in `.agyflow/docs/INDEX.md`. @@ -173,13 +173,13 @@ Standards live in `.agyflow/docs/standards/` and are indexed in `.agyflow/docs/I **Chain workflows by passing a task folder.** If you've completed a research or product-design workflow and want to build on those results, pass the task folder directly: ```bash -/development .agyflow/tasks/research/2026-01-12-oauth-research +/agyflow:development .agyflow/tasks/research/2026-01-12-oauth-research ``` You can also append additional instructions to narrow scope or guide the workflow: ```bash -/development .agyflow/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1 +/agyflow:development .agyflow/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1 ``` ## Known Issues @@ -187,10 +187,10 @@ You can also append additional instructions to narrow scope or guide the workflo **Orchestrator may stall after long phases.** After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state: ```bash -/development .agyflow/tasks/development/2026-03-24-my-feature +/agyflow:development .agyflow/tasks/development/2026-03-24-my-feature ``` ## Learn More - [Workflow Details](docs/workflows.md) - phases, examples, and task structure for each workflow type -- [Full Command Reference](docs/commands.md) - all workflow, review, utility, and quick commands +- [Full Skill Reference](docs/skills.md) - all workflow, review, utility, and quick skills diff --git a/agents/code-quality-pragmatist.md b/agents/code-quality-pragmatist.md index 264a202..382e648 100644 --- a/agents/code-quality-pragmatist.md +++ b/agents/code-quality-pragmatist.md @@ -41,7 +41,7 @@ The Task prompt MUST include: | Input | Source | Purpose | | ------------- | ----------------------- | ----------------------------------------------------------------------------------------- | -| `task_path` | Orchestrator or command | Path to task directory or code to review | +| `task_path` | Orchestrator or skill | Path to task directory or code to review | | `report_path` | Orchestrator (optional) | Where to write report (default: `verification/pragmatic-review.md` relative to task_path) | **CRITICAL**: All outputs MUST be written under `task_path`. Never write reports to project-level directories (`docs/`, `src/`, project root). diff --git a/agents/code-reviewer.md b/agents/code-reviewer.md index 332df57..4fe037b 100644 --- a/agents/code-reviewer.md +++ b/agents/code-reviewer.md @@ -1,6 +1,6 @@ --- name: code-reviewer -description: Automated code quality, security, and performance analysis. Analyzes code for complexity, duplication, security vulnerabilities, performance issues, and best practices compliance. Can run standalone (via command) or as part of implementation verification. Provides actionable findings categorized by severity. Read-only - reports issues without fixing. Does not interact with users. +description: Automated code quality, security, and performance analysis. Analyzes code for complexity, duplication, security vulnerabilities, performance issues, and best practices compliance. Can run standalone (via skill) or as part of implementation verification. Provides actionable findings categorized by severity. Read-only - reports issues without fixing. Does not interact with users. model: inherit color: orange mode: subagent @@ -43,8 +43,8 @@ The Task prompt MUST include: | Input | Source | Purpose | | --------------- | ----------------------- | ------------------------------------------------------------------------------------------- | -| `analysis_path` | Orchestrator or command | Path to analyze (file, directory, or task path) | -| `scope` | Orchestrator or command | `all` (default), `quality`, `security`, or `performance` | +| `analysis_path` | Orchestrator or skill | Path to analyze (file, directory, or task path) | +| `scope` | Orchestrator or skill | `all` (default), `quality`, `security`, or `performance` | | `report_path` | Orchestrator (optional) | Where to write report (default: `verification/code-review-report.md` relative to task_path) | **CRITICAL**: All outputs MUST be written under `task_path`. Never write reports to project-level directories (`docs/`, `src/`, project root). @@ -228,7 +228,7 @@ issue_counts: ## Integration -**Invoked by**: implementation-verifier (Phase 3), standalone via `/reviews-code` command +**Invoked by**: implementation-verifier (Phase 3), standalone via `/agyflow:reviews-code` skill **Prerequisites**: diff --git a/agents/production-readiness-checker.md b/agents/production-readiness-checker.md index 8116070..e5e3fa3 100644 --- a/agents/production-readiness-checker.md +++ b/agents/production-readiness-checker.md @@ -43,8 +43,8 @@ The Task prompt MUST include: | Input | Source | Purpose | | --------------- | ----------------------- | ---------------------------------------------------------------------------------------------------- | -| `analysis_path` | Orchestrator or command | Path to analyze (task directory, feature directory, or project) | -| `target` | Orchestrator or command | `production` (default, full rigor) or `staging` (relaxed) | +| `analysis_path` | Orchestrator or skill | Path to analyze (task directory, feature directory, or project) | +| `target` | Orchestrator or skill | `production` (default, full rigor) or `staging` (relaxed) | | `report_path` | Orchestrator (optional) | Where to write report (default: `verification/production-readiness-report.md` relative to task_path) | **CRITICAL**: All outputs MUST be written under `task_path`. Never write reports to project-level directories (`docs/`, `src/`, project root). @@ -268,7 +268,7 @@ issue_counts: ## Integration -**Invoked by**: implementation-verifier (Phase 3), performance orchestrator (Phase 4), standalone via `/reviews-production-readiness` command +**Invoked by**: implementation-verifier (Phase 3), performance orchestrator (Phase 4), standalone via `/agyflow:reviews-production-readiness` skill **Prerequisites**: diff --git a/agents/project-analyzer.md b/agents/project-analyzer.md index 18c9cfa..c7171c7 100644 --- a/agents/project-analyzer.md +++ b/agents/project-analyzer.md @@ -287,7 +287,7 @@ Return your analysis in the conversation response (do NOT create files): 1. **Structured JSON block**: Machine-readable analysis for downstream phases 2. **Markdown summary**: Human-readable overview for user review -**IMPORTANT**: Do NOT write any files to disk. The flow-init command will use your returned analysis to generate proper documentation in `.agyflow/docs/`. +**IMPORTANT**: Do NOT write any files to disk. The flow-init skill will use your returned analysis to generate proper documentation in `.agyflow/docs/`. --- @@ -399,6 +399,6 @@ Before returning your analysis, verify: 5. Identify conventions (naming, organization, documentation) 6. Generate structured report (JSON + markdown) -**Output**: Return structured analysis (JSON + markdown) in your response. Do NOT create files - the calling command handles file creation in `.agyflow/docs/`. +**Output**: Return structured analysis (JSON + markdown) in your response. Do NOT create files - the calling skill handles file creation in `.agyflow/docs/`. **Remember**: You are an analyzer, not a modifier. Read, analyze, return results in conversation. All findings must be evidence-based. diff --git a/agents/reality-assessor.md b/agents/reality-assessor.md index 8707a6d..ecb7f50 100644 --- a/agents/reality-assessor.md +++ b/agents/reality-assessor.md @@ -40,7 +40,7 @@ The Task prompt MUST include: | Input | Source | Purpose | | --------------------- | ----------------------- | -------------------------------------------------------------------------------------- | -| `task_path` | Orchestrator or command | Absolute path to task directory | +| `task_path` | Orchestrator or skill | Absolute path to task directory | | `report_path` | Orchestrator (optional) | Where to write report (default: `verification/reality-check.md` relative to task_path) | | `skip_test_execution` | Orchestrator (optional) | When `true`, read test results from file instead of running tests | | `test_results_path` | Orchestrator (optional) | Path to test results file (when `skip_test_execution: true`) | diff --git a/agents/task-classifier.md b/agents/task-classifier.md index 45055e7..5650e32 100644 --- a/agents/task-classifier.md +++ b/agents/task-classifier.md @@ -381,12 +381,12 @@ Use question with relevant options ## Integration Points -**With /work Command**: +**With /agyflow:work Skill**: -1. `/work` parses arguments and task description +1. `/agyflow:work` parses arguments and task description 2. Invokes this agent directly via Task tool 3. Agent performs classification and returns result -4. `/work` routes to appropriate orchestrator +4. `/agyflow:work` routes to appropriate orchestrator **Classification Routes**: diff --git a/docs/commands.md b/docs/skills.md similarity index 88% rename from docs/commands.md rename to docs/skills.md index 39f816e..3c288e8 100644 --- a/docs/commands.md +++ b/docs/skills.md @@ -1,15 +1,15 @@ -# Command Reference +# Skill Reference ## Unified Entry Point -### `/work [input]` +### `/agyflow:work [input]` Auto-classifies your task and routes to the appropriate workflow. Accepts: - **No arguments**: Extracts the task from your current conversation context -- Task description: `/work "Add user profile page"` -- Task folder path: `/work .agyflow/tasks/new-features/2026-02-17-user-profile` (resumes) -- GitHub issue URL: `/work https://github.com/org/repo/issues/42` +- Task description: `/agyflow:work "Add user profile page"` +- Task folder path: `/agyflow:work .agyflow/tasks/new-features/2026-02-17-user-profile` (resumes) +- GitHub issue URL: `/agyflow:work https://github.com/org/repo/issues/42` The plugin classifies the task type with confidence scoring, asks for confirmation, then launches the matching orchestrator. @@ -17,7 +17,7 @@ The plugin classifies the task type with confidence scoring, asks for confirmati ## Development -### `/development [description | task-path]` +### `/agyflow:development [description | task-path]` Starts the unified development workflow (14 adaptive phases) or resumes an existing one. All arguments are optional — when run without a description, the plugin extracts it from your current conversation. Pass an existing task path to resume. Task type (bug/enhancement/feature) is auto-detected from context when `--type` is omitted. @@ -38,7 +38,7 @@ Starts the unified development workflow (14 adaptive phases) or resumes an exist ## Performance -### `/performance [description | task-path]` +### `/agyflow:performance [description | task-path]` Starts performance optimization with static bottleneck analysis (9 phases) or resumes an existing one. Can be run without arguments — the plugin extracts the optimization target from your conversation. Detects N+1 queries, missing indexes, O(n^2) algorithms, blocking I/O, and memory leak patterns. @@ -56,7 +56,7 @@ You can optionally provide profiling data (flame graphs, APM screenshots) — th ## Migration -### `/migration [description | task-path]` +### `/agyflow:migration [description | task-path]` Starts migration workflow (8 phases) with mandatory rollback planning and risk assessment, or resumes an existing one. Can be run without arguments — the plugin extracts migration details from your conversation. @@ -73,7 +73,7 @@ Starts migration workflow (8 phases) with mandatory rollback planning and risk a ## Research -### `/research [question | task-path]` +### `/agyflow:research [question | task-path]` Starts research workflow (8 phases) with multi-source gathering, synthesis, and optional solution brainstorming, or resumes an existing one. Can be run without arguments — the plugin extracts the research question from your conversation. @@ -85,7 +85,7 @@ Starts research workflow (8 phases) with multi-source gathering, synthesis, and | `--from=PHASE` | Start from or resume at a specific phase | | `--reset-attempts` | Reset failed attempt counters (resume) | -Research output can feed into development: `/development --research=.agyflow/tasks/research/...` +Research output can feed into development: `/agyflow:development --research=.agyflow/tasks/research/...` **Task directory**: `.agyflow/tasks/research/` **Resume phases**: `foundation`, `brainstorming-decision`, `brainstorming`, `design`, `outputs`, `verification`, `integration` @@ -94,7 +94,7 @@ Research output can feed into development: `/development --research=.agyflow/tas ## Product Design -### `/product-design [description | task-path]` +### `/agyflow:product-design [description | task-path]` Starts the interactive product/feature design workflow (9 adaptive phases) or resumes an existing one. Transforms ideas into structured product briefs through collaborative exploration, iterative refinement, and visual prototyping. Can be run without arguments — the plugin extracts the design brief from your conversation. @@ -105,7 +105,7 @@ Starts the interactive product/feature design workflow (9 adaptive phases) or re | `--from=PHASE` | Start from or resume at a specific phase | | `--reset-attempts` | Reset failed attempt counters (resume) | -Design output can feed directly into development: `/development .agyflow/tasks/product-design/...` +Design output can feed directly into development: `/agyflow:development .agyflow/tasks/product-design/...` **Task directory**: `.agyflow/tasks/product-design/` **Resume phases**: `context`, `synthesis`, `problem`, `personas`, `alternatives`, `convergence`, `specification`, `prototyping`, `handoff` @@ -114,9 +114,9 @@ Design output can feed directly into development: `/development .agyflow/tasks/p ## Reviews & Audits -Standalone review commands that can be run anytime, independent of workflows. +Standalone review skills that can be run anytime, independent of workflows. -### `/reviews-code [path]` +### `/agyflow:reviews-code [path]` Automated code quality, security, and performance analysis. @@ -126,15 +126,15 @@ Automated code quality, security, and performance analysis. Analyzes complexity, duplication, code smells, security vulnerabilities, and performance issues. Generates report with severity levels (Critical/Warning/Info). -### `/reviews-pragmatic [path]` +### `/agyflow:reviews-pragmatic [path]` Detects over-engineering and ensures code matches project scale. Identifies excessive abstraction, enterprise patterns in simple code, infrastructure overkill. Recommends specific simplifications with before/after examples. -### `/reviews-reality-check [task-path]` +### `/agyflow:reviews-reality-check [task-path]` Validates that completed work actually solves the intended problem. Runs tests, checks end-to-end workflows, and evaluates error scenarios. Returns deployment decision: Ready / Issues Found / Not Ready. -### `/reviews-spec-audit [spec-path]` +### `/agyflow:reviews-spec-audit [spec-path]` Independent specification audit with senior auditor perspective. @@ -144,7 +144,7 @@ Independent specification audit with senior auditor perspective. Identifies ambiguities, missing details, and gaps. Uses external tools (GitHub CLI, Azure CLI) for verification. -### `/reviews-production-readiness [path]` +### `/agyflow:reviews-production-readiness [path]` Pre-deployment verification across 7 dimensions: configuration, monitoring, error handling, performance, security, deployment, and GO/NO-GO recommendation. @@ -156,7 +156,7 @@ Pre-deployment verification across 7 dimensions: configuration, monitoring, erro ## Standards -### `/flow-init [--standards-from=PATH]` +### `/agyflow:flow-init [--standards-from=PATH]` Initialize the agyflow framework. Scans your codebase with a project-analyzer subagent, presents findings for confirmation, then generates: @@ -170,7 +170,7 @@ Initialize the agyflow framework. Scans your codebase with a project-analyzer su If `.agyflow/` already exists, offers to backup, update, or cancel. -### `/standards-discover [--scope=SCOPE]` +### `/agyflow:standards-discover [--scope=SCOPE]` Auto-discovers coding standards from multiple sources in parallel: config files, source code patterns, documentation, pull requests, and CI/CD pipelines. @@ -184,7 +184,7 @@ Auto-discovers coding standards from multiple sources in parallel: config files, Presents findings in confidence tiers (high/medium/low) for review before applying. -### `/standards-update [description] [--from=PATH]` +### `/agyflow:standards-update [description] [--from=PATH]` Update or create standards from conversation context or explicit description. When run without arguments, scans your current conversation for standards patterns like "we should always...", "our convention is...", "prefer X over Y" and proposes them as new standards. @@ -194,11 +194,11 @@ Update or create standards from conversation context or explicit description. Wh --- -## Quick Commands +## Quick Skills -Lightweight commands for small tasks that don't need a full orchestrator workflow. +Lightweight skills for small tasks that don't need a full orchestrator workflow. -### `/quick-dev [task description]` +### `/agyflow:quick-dev [task description]` Implement a task directly with standards awareness. Reads INDEX.md, loads applicable standards, then implements without planning mode. @@ -207,7 +207,7 @@ Implement a task directly with standards awareness. Reads INDEX.md, loads applic **Task directory**: `.agyflow/tasks/quick-dev/YYYY-MM-DD-task-name/` **Artifacts**: `task.yml`, `summary.md` -### `/quick-plan [task description]` +### `/agyflow:quick-plan [task description]` Enter Google Antigravity CLI's planning mode with standards awareness. Discovers and reads applicable standards _before_ entering plan mode, so your plan is informed by project conventions. @@ -216,11 +216,11 @@ Standards compliance checklist is required in the plan file before exiting plan **Task directory**: `.agyflow/tasks/quick-plan/YYYY-MM-DD-task-name/` **Artifacts**: `task.yml` (+ `plan_path`), `analysis/findings.md` -### `/quick-bugfix [bug description]` +### `/agyflow:quick-bugfix [bug description]` Lightweight TDD-driven bug fix without a full orchestrator workflow. Analyzes the bug, writes a failing test, implements the fix, and verifies the test passes. -**When to use**: Simple, isolated bugs where you can quickly identify the root cause. If the bug is too complex (multiple files, unclear root cause, architectural impact), the skill suggests escalating to `/development`. +**When to use**: Simple, isolated bugs where you can quickly identify the root cause. If the bug is too complex (multiple files, unclear root cause, architectural impact), the skill suggests escalating to `/agyflow:development`. **Task directory**: `.agyflow/tasks/quick-bugfix/YYYY-MM-DD-task-name/` **Artifacts**: `task.yml`, `analysis/findings.md`, `summary.md` diff --git a/docs/workflows.md b/docs/workflows.md index f01664f..685f8bc 100644 --- a/docs/workflows.md +++ b/docs/workflows.md @@ -7,9 +7,9 @@ agyflow provides five workflow types, each with phases tailored to its needs. Al The unified development workflow handles features, enhancements, and bug fixes through a 14-phase adaptive pipeline. Phases activate or skip based on task type. ``` -/development -/development "Add two-factor authentication" -/development "Fix login timeout" --type=bug +/agyflow:development +/agyflow:development "Add two-factor authentication" +/agyflow:development "Fix login timeout" --type=bug ``` When run without arguments, the plugin extracts the task description from your conversation and auto-detects the type (feature, bug, or enhancement). Use `--type=` only when you want to override the auto-detection. @@ -40,7 +40,7 @@ When run without arguments, the plugin extracts the task description from your c Start development informed by a completed research workflow. Research context flows through all phases: ``` -/development "Implement OAuth" --research=.agyflow/tasks/research/2026-01-12-oauth-research +/agyflow:development "Implement OAuth" --research=.agyflow/tasks/research/2026-01-12-oauth-research ``` Research artifacts are copied to `analysis/research-context/` and summaries pass to every subagent. @@ -48,7 +48,7 @@ Research artifacts are copied to `analysis/research-context/` and summaries pass ### Resume ``` -/development [task-path] [--from=PHASE] [--reset-attempts] +/agyflow:development [task-path] [--from=PHASE] [--reset-attempts] ``` Resume phases: `analysis`, `gap`, `spec`, `plan`, `implement`, `verify` @@ -60,8 +60,8 @@ Resume phases: `analysis`, `gap`, `spec`, `plan`, `implement`, `verify` Static code analysis to detect bottlenecks, followed by standard spec/plan/implement/verify pipeline. ``` -/performance -/performance "Optimize dashboard loading time" +/agyflow:performance +/agyflow:performance "Optimize dashboard loading time" ``` ### Phases @@ -83,7 +83,7 @@ Static code analysis to detect bottlenecks, followed by standard spec/plan/imple ### Resume ``` -/performance [task-path] [--from=PHASE] [--reset-attempts] +/agyflow:performance [task-path] [--from=PHASE] [--reset-attempts] ``` Resume phases: `analysis`, `specification`, `planning`, `implementation`, `verification` @@ -95,8 +95,8 @@ Resume phases: `analysis`, `specification`, `planning`, `implementation`, `verif Technology, data, and architecture migrations with rollback planning and risk assessment. ``` -/migration -/migration "Migrate from REST to GraphQL" --type=code +/agyflow:migration +/agyflow:migration "Migrate from REST to GraphQL" --type=code ``` **Migration types**: `code`, `data`, `architecture`, `general` @@ -124,7 +124,7 @@ Technology, data, and architecture migrations with rollback planning and risk as ### Resume ``` -/migration [task-path] [--from=PHASE] [--reset-attempts] +/agyflow:migration [task-path] [--from=PHASE] [--reset-attempts] ``` Resume phases: `analysis`, `target`, `spec`, `plan`, `execute`, `verify`, `docs` @@ -136,8 +136,8 @@ Resume phases: `analysis`, `target`, `spec`, `plan`, `execute`, `verify`, `docs` Multi-source research with synthesis, optional solution brainstorming, and high-level design. ``` -/research -/research "What authentication approach fits our architecture?" --type=technical +/agyflow:research +/agyflow:research "What authentication approach fits our architecture?" --type=technical ``` **Research types**: `technical`, `requirements`, `literature`, `mixed` @@ -162,7 +162,7 @@ Information gathering runs parallel subagents across multiple source categories ### Resume ``` -/research [task-path] [--from=PHASE] [--reset-attempts] +/agyflow:research [task-path] [--from=PHASE] [--reset-attempts] ``` Resume phases: `foundation`, `brainstorming-decision`, `brainstorming`, `design`, `outputs`, `verification`, `integration` @@ -174,9 +174,9 @@ Resume phases: `foundation`, `brainstorming-decision`, `brainstorming`, `design` Interactive workflow for designing features and products before building them. Transforms ideas into structured product briefs through collaborative exploration, iterative refinement, and visual prototyping. Phases adapt based on design characteristics (greenfield vs enhancement, simple vs complex, UI-focused vs backend). ``` -/product-design -/product-design "Design a dashboard for monitoring API usage" -/product-design --research=.agyflow/tasks/research/2026-01-12-auth-research +/agyflow:product-design +/agyflow:product-design "Design a dashboard for monitoring API usage" +/agyflow:product-design --research=.agyflow/tasks/research/2026-01-12-auth-research ``` When run without arguments, the plugin extracts the design brief from your conversation. @@ -202,13 +202,13 @@ Phases 2, 5, and 6 include iterative refinement loops — you can request revisi The output is a structured product brief that can be passed directly to the development workflow: ``` -/development .agyflow/tasks/product-design/2026-03-10-api-dashboard +/agyflow:development .agyflow/tasks/product-design/2026-03-10-api-dashboard ``` ### Resume ``` -/product-design [task-path] [--from=PHASE] [--reset-attempts] +/agyflow:product-design [task-path] [--from=PHASE] [--reset-attempts] ``` Resume phases: `context`, `synthesis`, `problem`, `personas`, `alternatives`, `convergence`, `specification`, `prototyping`, `handoff` diff --git a/skills/development/SKILL.md b/skills/development/SKILL.md index 0ded5b3..ad974bc 100644 --- a/skills/development/SKILL.md +++ b/skills/development/SKILL.md @@ -619,7 +619,7 @@ When starting development from a completed research task, the orchestrator loads **Method 1: Research folder as sole argument** (recommended) ``` -/development .agyflow/tasks/research/2026-01-12-oauth-research +/agyflow:development .agyflow/tasks/research/2026-01-12-oauth-research ``` The orchestrator auto-detects this is a research folder and: @@ -631,7 +631,7 @@ The orchestrator auto-detects this is a research folder and: **Method 2: Explicit --research flag** ``` -/development "Implement OAuth" --research=.agyflow/tasks/research/2026-01-12-oauth-research +/agyflow:development "Implement OAuth" --research=.agyflow/tasks/research/2026-01-12-oauth-research ``` ### Research Artifacts (Standard List) @@ -659,12 +659,12 @@ When research context is detected, read these files from the research folder: --- -## Command Integration +## Skill Integration Invoked via: -- `/development [description] [--e2e] [--user-docs] [--research=PATH]` (new) -- `/development [task-path] [--from=PHASE] [--reset-attempts]` (resume) +- `/agyflow:development [description] [--e2e] [--user-docs] [--research=PATH]` (new) +- `/agyflow:development [task-path] [--from=PHASE] [--reset-attempts]` (resume) --- diff --git a/skills/docs-manager/SKILL.md b/skills/docs-manager/SKILL.md index d66878b..f888d07 100644 --- a/skills/docs-manager/SKILL.md +++ b/skills/docs-manager/SKILL.md @@ -118,7 +118,7 @@ Use this when a project doesn't have `.agyflow/docs/` or needs documentation for _Not initialized for this project. If you need frontend standards, you can:_ - _Add them manually using the docs-manager skill_ - - _Run `/standards-discover --scope=frontend` to auto-discover_ + - _Run `/agyflow:standards-discover --scope=frontend` to auto-discover_ ``` 6. **MANDATORY - Update AGENTS.md:** @@ -144,7 +144,7 @@ Use this when a project doesn't have `.agyflow/docs/` or needs documentation for **Note on Skipped Standards**: If standard categories are skipped during initialization, teams can add them later using: - "Add Documentation File" operation to add specific standards -- `/standards-discover` command to auto-discover standards from codebase +- `/agyflow:standards-discover` skill to auto-discover standards from codebase --- diff --git a/skills/docs-manager/references/agents-md-template.md b/skills/docs-manager/references/agents-md-template.md index 0b5fd0d..9f52a0c 100644 --- a/skills/docs-manager/references/agents-md-template.md +++ b/skills/docs-manager/references/agents-md-template.md @@ -21,9 +21,9 @@ When you notice recurring patterns, fixes, or conventions during implementation - The same type of fix is needed across multiple files - A new library/pattern is adopted that should be documented -When this happens, briefly suggest the standard to the user. If approved, invoke `/standards-update` with the identified pattern. +When this happens, briefly suggest the standard to the user. If approved, invoke `/agyflow:standards-update` with the identified pattern. ## agyflow Workflows -This project uses the agyflow plugin for structured development workflows. When any `/*` command is invoked, execute it via the Skill tool immediately — do not skip workflows for "straightforward" tasks. The user chose the workflow intentionally; complexity assessment is the workflow's job. +This project uses the agyflow plugin for structured development workflows. When any `/agyflow:*` skill is invoked, execute it via the Skill tool immediately — do not skip workflows for "straightforward" tasks. The user chose the workflow intentionally; complexity assessment is the workflow's job. ``` diff --git a/skills/flow-init/SKILL.md b/skills/flow-init/SKILL.md index af8ecd8..08dd796 100644 --- a/skills/flow-init/SKILL.md +++ b/skills/flow-init/SKILL.md @@ -188,7 +188,7 @@ Wait for docs-operator to complete, then immediately continue with Step 2. - Next steps: 1. Review generated documentation 2. Customize for your team - 3. Start development with `/work` + 3. Start development with `/agyflow:work` 4. Keep documentation current --- diff --git a/skills/migration/SKILL.md b/skills/migration/SKILL.md index 6921d22..875b64d 100644 --- a/skills/migration/SKILL.md +++ b/skills/migration/SKILL.md @@ -350,11 +350,11 @@ Refer to the template [src/templates/orchestrator-state-migration.yml](../../tem --- -## Command Integration +## Skill Integration Invoked via: -- `/migration [description] [--type=TYPE]` (new) -- `/migration [task-path] [--from=PHASE]` (resume) +- `/agyflow:migration [description] [--type=TYPE]` (new) +- `/agyflow:migration [task-path] [--from=PHASE]` (resume) Task directory: `.agyflow/tasks/migrations/YYYY-MM-DD-task-name/` diff --git a/skills/performance/SKILL.md b/skills/performance/SKILL.md index 7d5d77d..2ab87b3 100644 --- a/skills/performance/SKILL.md +++ b/skills/performance/SKILL.md @@ -391,11 +391,11 @@ Refer to the template [src/templates/orchestrator-state-performance.yml](../../t --- -## Command Integration +## Skill Integration Invoked via: -- `/performance [description]` (new) -- `/performance [task-path] [--from=PHASE]` (resume) +- `/agyflow:performance [description]` (new) +- `/agyflow:performance [task-path] [--from=PHASE]` (resume) Task directory: `.agyflow/tasks/performance/YYYY-MM-DD-task-name/` diff --git a/skills/product-design/SKILL.md b/skills/product-design/SKILL.md index 8053d2f..3ee5352 100644 --- a/skills/product-design/SKILL.md +++ b/skills/product-design/SKILL.md @@ -57,7 +57,7 @@ Starting Phase 0: Initialize & Gather Context... Use for **product and feature design**: defining what to build before building it. Greenfield products, new features, enhancements, API designs, workflow designs. -**DO NOT use for**: Implementation tasks (use `/development`), pure research (use `/research`), bug fixes, performance optimization, migrations. +**DO NOT use for**: Implementation tasks (use `/agyflow:development`), pure research (use `/agyflow:research`), bug fixes, performance optimization, migrations. **When to use this vs development orchestrator**: If you need to explore the problem space, evaluate alternatives, and define requirements interactively before any code is written, use this. If you already know what to build and need to plan and execute, use development. @@ -701,7 +701,7 @@ question — with options: Product brief approved and saved to: [task-path]/outputs/product-brief.md To start development based on this design, clear context first or start a new session, then run: -/development [task-path] +/agyflow:development [task-path] ``` **Output**: `outputs/product-brief.md` @@ -759,12 +759,12 @@ Refer to the template [src/templates/orchestrator-state-product-design.yml](../. --- -## Command Integration +## Skill Integration Invoked via: -- `/product-design [description] [--no-visual] [--research=PATH]` (new) -- `/product-design [task-path] [--from=PHASE]` (resume) +- `/agyflow:product-design [description] [--no-visual] [--research=PATH]` (new) +- `/agyflow:product-design [task-path] [--from=PHASE]` (resume) **Flags**: | Flag | Effect | @@ -786,7 +786,7 @@ Task directory: `.agyflow/tasks/product-design/YYYY-MM-DD-task-name/` The product brief is consumed by the development orchestrator: ``` -/development .agyflow/tasks/product-design/YYYY-MM-DD-task-name/ +/agyflow:development .agyflow/tasks/product-design/YYYY-MM-DD-task-name/ ``` The development orchestrator auto-detects the product-design task type and copies the product brief to `analysis/design-context/product-brief.md`, then flows design context through all development phases. The product brief's Layer 0 maps to requirements, design characteristics map to task characteristics, and mockup references feed into UI implementation phases. @@ -796,7 +796,7 @@ The development orchestrator auto-detects the product-design task type and copie A completed research workflow can feed into product design: ``` -/product-design "Design feature X" --research=.agyflow/tasks/research/YYYY-MM-DD-research/ +/agyflow:product-design "Design feature X" --research=.agyflow/tasks/research/YYYY-MM-DD-research/ ``` Research findings are imported into `context/research-context/` and synthesized alongside other context sources in Phase 1. diff --git a/skills/quick-bugfix/SKILL.md b/skills/quick-bugfix/SKILL.md index c7737ef..3e1111b 100644 --- a/skills/quick-bugfix/SKILL.md +++ b/skills/quick-bugfix/SKILL.md @@ -9,25 +9,25 @@ user-invocable: true Lightweight TDD-driven bug fix workflow with planning mode. Analyze the bug, present a fix plan for approval, then reproduce with a failing test, fix, and verify. No orchestrator state, no subagents. Creates lightweight task directory for artifact anchoring. -For complex bugs that grow beyond a quick fix, suggests escalating to the full development workflow (`/development`). +For complex bugs that grow beyond a quick fix, suggests escalating to the full development workflow (`/agyflow:development`). ## Usage ```bash -/quick-bugfix "Login form submits twice on slow connections" -/quick-bugfix "API returns 500 when email contains special characters" -/quick-bugfix "Dark mode toggle doesn't persist after refresh" +/agyflow:quick-bugfix "Login form submits twice on slow connections" +/agyflow:quick-bugfix "API returns 500 when email contains special characters" +/agyflow:quick-bugfix "Dark mode toggle doesn't persist after refresh" ``` ## When to Use -**Use `/quick-bugfix` when:** +**Use `/agyflow:quick-bugfix` when:** - Bug is reasonably scoped and reproducible - You have a clear description of expected vs actual behavior - Fix likely touches a small number of files -**Use `/development` instead when:** +**Use `/agyflow:development` instead when:** - Bug requires architectural changes - Multiple subsystems are involved @@ -79,7 +79,7 @@ For complex bugs that grow beyond a quick fix, suggests escalating to the full d **If not exists:** - Note that no standards are available -- Suggest running `/flow-init` in completion message +- Suggest running `/agyflow:flow-init` in completion message ### Standards Reading Enforcement (MANDATORY) @@ -165,7 +165,7 @@ Use question: 1. Ensure `analysis/findings.md` is written (above) 2. Update `task.yml`: set `status: escalated`, `escalation_reason: "[signals detected]"`, `updated: [now]` -3. Tell the user: "Run `/development .agyflow/tasks/quick-bugfix/YYYY-MM-DD-task-name` to continue with full workflow." +3. Tell the user: "Run `/agyflow:development .agyflow/tasks/quick-bugfix/YYYY-MM-DD-task-name` to continue with full workflow." 4. Do NOT set `escalated_to` — the development orchestrator will set it 5. `summary.md` is NOT written on escalation @@ -198,7 +198,7 @@ Standards context from Step 3 and analysis from Step 4 MUST inform the plan. ## Applicable Standards [List each standard file read, with key guidelines extracted from each. -If no standards exist: "No AI SDLC standards found. Consider running `/flow-init`."] +If no standards exist: "No AI SDLC standards found. Consider running `/agyflow:flow-init`."] ## Standards Compliance Checklist @@ -256,7 +256,7 @@ If any section is missing, add it before asking for user approval. **If still failing after 3 attempts:** - Stop and present findings to the user -- Suggest escalating to `/development` for a more thorough approach +- Suggest escalating to `/agyflow:development` for a more thorough approach ### Step 8: Summary @@ -265,7 +265,7 @@ If any section is missing, add it before asking for user approval. ```markdown # Task Summary -**Command**: quick-bugfix +**Skill**: quick-bugfix **Date**: YYYY-MM-DD **Status**: completed @@ -315,6 +315,6 @@ If any section is missing, add it before asking for user approval. Proceed with the bug fix normally, then note: ``` -"No AI SDLC standards found. Consider running `/flow-init` to initialize +"No AI SDLC standards found. Consider running `/agyflow:flow-init` to initialize project documentation and coding standards for better consistency." ``` diff --git a/skills/quick-dev/SKILL.md b/skills/quick-dev/SKILL.md index 0022d01..72d77fd 100644 --- a/skills/quick-dev/SKILL.md +++ b/skills/quick-dev/SKILL.md @@ -10,29 +10,29 @@ Implement a task directly without entering planning mode, while still applying p ## Usage ```bash -/quick-dev [task description] +/agyflow:quick-dev [task description] ``` ## Examples ```bash -/quick-dev "Add a logout button to the navbar" -/quick-dev "Fix the typo in the error message" -/quick-dev "Update the API endpoint to accept JSON" +/agyflow:quick-dev "Add a logout button to the navbar" +/agyflow:quick-dev "Fix the typo in the error message" +/agyflow:quick-dev "Update the API endpoint to accept JSON" ``` --- ## When to Use -**Use `/quick-dev` when:** +**Use `/agyflow:quick-dev` when:** - Task is clear and well-defined - You know what needs to be done - No architectural decisions needed - Quick fixes, small features, or straightforward changes -**Use `/quick-plan` instead when:** +**Use `/agyflow:quick-plan` instead when:** - Task scope is uncertain - Multiple implementation approaches possible @@ -81,7 +81,7 @@ Implement a task directly without entering planning mode, while still applying p **If not exists:** - Note that no standards are available -- Suggest running `/flow-init` in completion message +- Suggest running `/agyflow:flow-init` in completion message ### Standards Reading Enforcement (MANDATORY) @@ -127,7 +127,7 @@ Implement a task directly without entering planning mode, while still applying p ```markdown # Task Summary -**Command**: quick-dev +**Skill**: quick-dev **Date**: YYYY-MM-DD **Status**: completed @@ -181,6 +181,6 @@ Implement a task directly without entering planning mode, while still applying p Proceed with implementation normally, then note: ``` -"No AI SDLC standards found. Consider running `/flow-init` to initialize +"No AI SDLC standards found. Consider running `/agyflow:flow-init` to initialize project documentation and coding standards for better consistency." ``` diff --git a/skills/quick-plan/SKILL.md b/skills/quick-plan/SKILL.md index 96a2780..47aedf1 100644 --- a/skills/quick-plan/SKILL.md +++ b/skills/quick-plan/SKILL.md @@ -10,15 +10,15 @@ Enter Google Antigravity CLI's planning mode for a task, with automatic discover ## Usage ```bash -/quick-plan [task description] +/agyflow:quick-plan [task description] ``` ## Examples ```bash -/quick-plan "Add user authentication with email/password" -/quick-plan "Refactor the payment processing module" -/quick-plan +/agyflow:quick-plan "Add user authentication with email/password" +/agyflow:quick-plan "Refactor the payment processing module" +/agyflow:quick-plan ``` --- @@ -109,7 +109,7 @@ The planning mode will: **BLOCKING: Do NOT call ask user for approval until the plan file contains these sections:** -1. **"## Applicable Standards"** — list each standard file that was read, with key guidelines extracted from each. If no standards exist, state: "No AI SDLC standards found. Consider running `/flow-init`." +1. **"## Applicable Standards"** — list each standard file that was read, with key guidelines extracted from each. If no standards exist, state: "No AI SDLC standards found. Consider running `/agyflow:flow-init`." 2. **"## Standards Compliance Checklist"** — checkboxes for each applicable standard guideline that implementation must follow. Example: ```markdown @@ -127,7 +127,7 @@ If these sections are missing from the plan file, add them before asking user fo Continue with planning mode normally. The "Applicable Standards" section in the plan should note: ``` -No AI SDLC standards found. Consider running `/flow-init` to initialize +No AI SDLC standards found. Consider running `/agyflow:flow-init` to initialize project documentation and coding standards for better consistency. ``` diff --git a/skills/research/SKILL.md b/skills/research/SKILL.md index 4ba5f95..de338f1 100644 --- a/skills/research/SKILL.md +++ b/skills/research/SKILL.md @@ -358,7 +358,7 @@ question - "Design complete. Continue to output generation?" 3. If design artifacts exist, suggest starting development in a fresh session: ``` To start development based on this research, clear context first or start a new session, then run: - /development [task-path] + /agyflow:development [task-path] ``` → End of workflow @@ -419,7 +419,7 @@ Refer to the template [src/templates/orchestrator-state-research.yml](../../temp ### As Standalone Research -**Command**: `/research [research-question]` +**Skill**: `/agyflow:research [research-question]` **Flow**: Complete all phases, save outputs in task directory ### As Embedded Research Phase @@ -439,12 +439,12 @@ Refer to `research_outputs` in the template [src/templates/orchestrator-state-re --- -## Command Integration +## Skill Integration Invoked via: -- `/research [question] [--type=TYPE] [--brainstorm] [--no-brainstorm] [--design] [--no-design]` (new) -- `/research [task-path] [--from=PHASE]` (resume) +- `/agyflow:research [question] [--type=TYPE] [--brainstorm] [--no-brainstorm] [--design] [--no-design]` (new) +- `/agyflow:research [task-path] [--from=PHASE]` (resume) **Brainstorming flags**: diff --git a/skills/reviews-code/SKILL.md b/skills/reviews-code/SKILL.md index c88b32e..1162032 100644 --- a/skills/reviews-code/SKILL.md +++ b/skills/reviews-code/SKILL.md @@ -54,19 +54,19 @@ The code-reviewer subagent will: **Example 1**: Review specific task ``` -User: /reviews-code .agyflow/tasks/development/2025-10-24-auth/ +User: /agyflow:reviews-code .agyflow/tasks/development/2025-10-24-auth/ ``` **Example 2**: Review with specific scope ``` -User: /reviews-code src/api/ --scope=security +User: /agyflow:reviews-code src/api/ --scope=security ``` **Example 3**: Review entire project ``` -User: /reviews-code src/ +User: /agyflow:reviews-code src/ ``` ## What to Expect diff --git a/skills/reviews-pragmatic/SKILL.md b/skills/reviews-pragmatic/SKILL.md index 7c46f04..e0eab55 100644 --- a/skills/reviews-pragmatic/SKILL.md +++ b/skills/reviews-pragmatic/SKILL.md @@ -60,19 +60,19 @@ The code-quality-pragmatist agent will: **Example 1**: Review specific feature ``` -User: /reviews-pragmatic .agyflow/tasks/development/2025-11-17-user-management/ +User: /agyflow:reviews-pragmatic .agyflow/tasks/development/2025-11-17-user-management/ ``` **Example 2**: Review source directory ``` -User: /reviews-pragmatic src/features/payments/ +User: /agyflow:reviews-pragmatic src/features/payments/ ``` **Example 3**: Review specific file ``` -User: /reviews-pragmatic src/services/cache-service.ts +User: /agyflow:reviews-pragmatic src/services/cache-service.ts ``` ## What to Expect diff --git a/skills/reviews-production-readiness/SKILL.md b/skills/reviews-production-readiness/SKILL.md index 8c910b4..4453ba5 100644 --- a/skills/reviews-production-readiness/SKILL.md +++ b/skills/reviews-production-readiness/SKILL.md @@ -55,19 +55,19 @@ The production-readiness-checker subagent will: **Example 1**: Check specific task for production ``` -User: /reviews-production-readiness .agyflow/tasks/development/2025-10-24-payment-api/ +User: /agyflow:reviews-production-readiness .agyflow/tasks/development/2025-10-24-payment-api/ ``` **Example 2**: Check feature for staging ``` -User: /reviews-production-readiness src/features/notifications/ --target=staging +User: /agyflow:reviews-production-readiness src/features/notifications/ --target=staging ``` **Example 3**: Comprehensive project check ``` -User: /reviews-production-readiness . +User: /agyflow:reviews-production-readiness . ``` ## What to Expect diff --git a/skills/reviews-reality-check/SKILL.md b/skills/reviews-reality-check/SKILL.md index c8bc842..f9ff7f3 100644 --- a/skills/reviews-reality-check/SKILL.md +++ b/skills/reviews-reality-check/SKILL.md @@ -68,19 +68,19 @@ The reality-assessor agent will: **Example 1**: Reality check before deployment ``` -User: /reviews-reality-check .agyflow/tasks/development/2025-11-17-payment-processing/ +User: /agyflow:reviews-reality-check .agyflow/tasks/development/2025-11-17-payment-processing/ ``` **Example 2**: Verify claimed completion ``` -User: /reviews-reality-check .agyflow/tasks/development/2025-11-17-login-timeout/ +User: /agyflow:reviews-reality-check .agyflow/tasks/development/2025-11-17-login-timeout/ ``` **Example 3**: Production readiness check ``` -User: /reviews-reality-check .agyflow/tasks/development/2025-11-17-user-dashboard/ --production +User: /agyflow:reviews-reality-check .agyflow/tasks/development/2025-11-17-user-dashboard/ --production ``` ## What to Expect diff --git a/skills/reviews-spec-audit/SKILL.md b/skills/reviews-spec-audit/SKILL.md index f18d3bd..4481627 100644 --- a/skills/reviews-spec-audit/SKILL.md +++ b/skills/reviews-spec-audit/SKILL.md @@ -73,19 +73,19 @@ The spec-auditor agent will: **Example 1**: Pre-implementation spec audit ``` -User: /reviews-spec-audit .agyflow/tasks/development/2025-11-17-user-auth/implementation/spec.md +User: /agyflow:reviews-spec-audit .agyflow/tasks/development/2025-11-17-user-auth/implementation/spec.md ``` **Example 2**: Post-implementation audit ``` -User: /reviews-spec-audit .agyflow/tasks/development/2025-11-17-user-auth/ --post-implementation +User: /agyflow:reviews-spec-audit .agyflow/tasks/development/2025-11-17-user-auth/ --post-implementation ``` **Example 3**: Audit with clarification focus ``` -User: /reviews-spec-audit spec.md --focus=ambiguity +User: /agyflow:reviews-spec-audit spec.md --focus=ambiguity ``` ## What to Expect diff --git a/skills/standards-discover/SKILL.md b/skills/standards-discover/SKILL.md index cfcb5db..f16b3db 100644 --- a/skills/standards-discover/SKILL.md +++ b/skills/standards-discover/SKILL.md @@ -67,7 +67,7 @@ Custom scope values are matched against existing `.agyflow/docs/standards/*/` di ### Phase 1: Planning & Initialization 1. **Parse options** from command arguments -2. **Check prerequisites**: Verify `.agyflow/docs/` exists. If not, offer to run `/flow-init` first +2. **Check prerequisites**: Verify `.agyflow/docs/` exists. If not, offer to run `/agyflow:flow-init` first 3. **Read existing standards** from `.agyflow/docs/INDEX.md` to identify updates vs creates and avoid duplicates 4. **Display discovery plan** showing scope, sources, and estimated time 5. **Get user confirmation** via question before proceeding @@ -196,7 +196,7 @@ Display final results: | Situation | Strategy | | ------------------------ | ----------------------------------------------------- | -| `.agyflow/docs/` missing | Offer `/flow-init`, abort if declined | +| `.agyflow/docs/` missing | Offer `/agyflow:flow-init`, abort if declined | | gh CLI unavailable | Skip PR analysis, continue with other sources | | GitHub API rate limit | Skip PR analysis, note in report | | Config file parse error | Skip that file, log warning, continue | @@ -212,7 +212,7 @@ Display final results: | ------------------------------------ | ---------------------------------------------------------------- | | `docs-manager` skill | Creates/updates standard files, regenerates INDEX.md | | `implementation-plan-executor` skill | Discovered standards immediately available via INDEX.md | -| `standards-update` command | Complementary: discover = automated bulk, update = manual single | +| `standards-update` skill | Complementary: discover = automated bulk, update = manual single | --- @@ -220,17 +220,17 @@ Display final results: ```bash # Full discovery (default) -/standards-discover +/agyflow:standards-discover # Quick scan (config files only, ~30-60s) -/standards-discover --scope=quick +/agyflow:standards-discover --scope=quick # Frontend standards only -/standards-discover --scope=frontend +/agyflow:standards-discover --scope=frontend # High confidence, auto-apply -/standards-discover --confidence=80 --auto-apply +/agyflow:standards-discover --confidence=80 --auto-apply # Skip external analysis (offline/no GitHub) -/standards-discover --skip-external +/agyflow:standards-discover --skip-external ``` diff --git a/skills/standards-update/SKILL.md b/skills/standards-update/SKILL.md index 6f615f0..c70dfd3 100644 --- a/skills/standards-update/SKILL.md +++ b/skills/standards-update/SKILL.md @@ -12,9 +12,9 @@ Update or create standards in `.agyflow/docs/standards/` based on conversation c ## Usage ```bash -/standards-update # Detect from conversation -/standards-update "always use React.memo for lists" # From description -/standards-update --from=/path/to/other-project # Sync from another project +/agyflow:standards-update # Detect from conversation +/agyflow:standards-update "always use React.memo for lists" # From description +/agyflow:standards-update --from=/path/to/other-project # Sync from another project ``` --- @@ -27,7 +27,7 @@ When `--from=PATH` is provided, the skill switches to **sync mode** — importin 1. Resolve the path (absolute or relative to cwd) 2. Check `PATH/.agyflow/docs/standards/` exists. If not, inform the user and stop. -3. Check `.agyflow/docs/standards/` exists in the current project. If not, offer to run `/flow-init` first. +3. Check `.agyflow/docs/standards/` exists in the current project. If not, offer to run `/agyflow:flow-init` first. ### SYNC STEP 2: Analyze Differences @@ -156,4 +156,4 @@ Wait for docs-operator to complete, then immediately proceed to Phase 5. ## Prerequisites -If `.agyflow/docs/` doesn't exist, offer to run `/flow-init` first. +If `.agyflow/docs/` doesn't exist, offer to run `/agyflow:flow-init` first. diff --git a/skills/work/SKILL.md b/skills/work/SKILL.md index 09ab7e8..a9ca3f6 100644 --- a/skills/work/SKILL.md +++ b/skills/work/SKILL.md @@ -1,9 +1,9 @@ --- name: work -description: Unified entry point — auto-classifies tasks and routes to appropriate workflow. ALWAYS execute when invoked via slash command. +description: Unified entry point — auto-classifies tasks and routes to appropriate workflow. ALWAYS execute when invoked via slash skill. --- -**NOTE**: This is a multi-step workflow that invokes the task-classifier subagent and orchestrator skills at specific steps. The `` tag refers to THIS command only — you MUST still use the Skill tool to invoke those other skills when instructed below. Follow ALL steps in order. +**NOTE**: This is a multi-step workflow that invokes the task-classifier subagent and orchestrator skills at specific steps. The `` tag refers to THIS skill only — you MUST still use the Skill tool to invoke those other skills when instructed below. Follow ALL steps in order. # Unified Work Entry Point @@ -12,7 +12,7 @@ Auto-classifies tasks and routes to the appropriate workflow orchestrator. Suppo ## Usage ```bash -/work [task description | task folder path | issue identifier] +/agyflow:work [task description | task folder path | issue identifier] ``` ### Input Types @@ -31,18 +31,18 @@ Auto-classifies tasks and routes to the appropriate workflow orchestrator. Suppo ```bash # Resume existing task -/work ".agyflow/tasks/development/2025-10-23-login-timeout" -/work "2025-10-26-user-auth" +/agyflow:work ".agyflow/tasks/development/2025-10-23-login-timeout" +/agyflow:work "2025-10-26-user-auth" # New task (auto-classifies) -/work "Fix login timeout error on mobile devices" -/work "Add user authentication with email/password" -/work "Improve dashboard loading performance" +/agyflow:work "Fix login timeout error on mobile devices" +/agyflow:work "Add user authentication with email/password" +/agyflow:work "Improve dashboard loading performance" # From issue tracker -/work "#456" -/work "PROJ-123" -/work "AB#789" +/agyflow:work "#456" +/agyflow:work "PROJ-123" +/agyflow:work "AB#789" ``` ## How It Works @@ -227,9 +227,9 @@ Then route to selected workflow using Skill tool. ``` Display: "Task cancelled. You can: -- Run /work again when ready -- Use specific workflow commands directly: - /development, /performance, etc." +- Run /agyflow:work again when ready +- Use specific workflow skills directly: + /agyflow:development, /agyflow:performance, etc." ``` --- @@ -250,7 +250,7 @@ Display: ### With Task Classifier -The `/work` command delegates classification to the task-classifier subagent via Task tool, which: +The `/agyflow:work` skill delegates classification to the task-classifier subagent via Task tool, which: - Fetches issue details from GitHub/Jira/Azure DevOps (via MCP, CLI tools, or WebFetch) - Analyzes codebase context for better classification @@ -259,7 +259,7 @@ The `/work` command delegates classification to the task-classifier subagent via ### With Orchestrators -After classification/detection, this command routes to the appropriate orchestrator via Skill tool: +After classification/detection, this skill routes to the appropriate orchestrator via Skill tool: - Each orchestrator handles its specific workflow (spec, plan, implement, verify, etc.) - State is persisted in `orchestrator-state.yml` for pause/resume @@ -276,7 +276,7 @@ Uses project documentation for context: ## Key Behaviors -1. **Single entry point** - One command for all workflow types +1. **Single entry point** - One skill for all workflow types 2. **Auto-classification** - Intelligent routing based on task description 3. **Resume support** - Detects and resumes existing tasks 4. **Issue integration** - Fetches details from GitHub/Jira/Azure DevOps diff --git a/templates/quick-bugfix-task.yml b/templates/quick-bugfix-task.yml index c7dabc3..ceec7ab 100644 --- a/templates/quick-bugfix-task.yml +++ b/templates/quick-bugfix-task.yml @@ -1,4 +1,4 @@ -command: quick-bugfix +skill: quick-bugfix title: "Short title from bug description" description: "Full bug description as provided by user" status: in_progress diff --git a/templates/quick-dev-task.yml b/templates/quick-dev-task.yml index f8a4ba7..a4728f8 100644 --- a/templates/quick-dev-task.yml +++ b/templates/quick-dev-task.yml @@ -1,4 +1,4 @@ -command: quick-dev +skill: quick-dev title: "Short title from task description" description: "Full task description as provided by user" status: in_progress diff --git a/templates/quick-plan-task.yml b/templates/quick-plan-task.yml index 7d02ea9..e689e8a 100644 --- a/templates/quick-plan-task.yml +++ b/templates/quick-plan-task.yml @@ -1,4 +1,4 @@ -command: quick-plan +skill: quick-plan title: "Short title from task description" description: "Full task description as provided by user" status: in_progress