@ancleto/spec 0.6.5 → 0.6.7

package/commands/cleto-ff.md

@@ -2,126 +2,8 @@
 description: Create a change and generate all artifacts needed for implementation in one go
 ---
 
-Fast-forward through artifact creation - generate everything needed to start implementation.
+Invoke the `ancleto-ff` skill with the Skill tool and follow it exactly; do not improvise steps.
 
 **Input**: The argument after `/cleto-ff` is the change name (kebab-case), OR a description of what the user wants to build.
 
-**Steps**
-
-1. **Resolve Work Item context and derive change name**
-
-   Resolve Work Item context in this order — stop at the first source that yields data:
-
-   a. **In-session context** — If WI data was already fetched in this session, use it. Proceed to name derivation below.
-   b. **`context.md`** — If a change name was provided as argument and `aspec/changes/<name>/context.md` exists, read it and use its content. Proceed to name derivation.
-   c. **Ask the user** — Use the **AskUserQuestion tool** to ask for the Work Item reference. Two accepted formats:
-
-   - **ID + Project** — e.g., ID `12345` and project `MyProject`
-   - **Full URL** — e.g., `https://dev.azure.com/org/MyProject/_workitems/edit/12345`
-
-   > "Do you have an Azure DevOps Work Item for this change? Provide the Work Item ID and Azure DevOps project name (e.g., ID: `12345`, Project: `MyProject`), or paste the full Work Item URL. Skip to describe the change manually."
-
-   **If WI provided:**
-
-   - If URL provided: extract numeric ID (pattern: `_workitems/edit/{id}`) AND project name (pattern: `/{org}/{project}/_workitems/`)
-   - Use BOTH `id` AND `project` when calling the AzDO MCP (`wit_get_work_item`) — never call with ID alone
-   - Extract from the response: `System.Id`, `System.Title`, `System.Description`, `Microsoft.VSTS.Common.AcceptanceCriteria`, `System.WorkItemType`
-   - Suggest a kebab-case name derived from `System.Title` (e.g., "Add payment gateway" → `add-payment-gateway`)
-   - Let the user accept or modify the suggested name before proceeding
-
-   **If skipped:**
-
-   - Display: "No work item linked — consider linking one for traceability."
-   - If no change name was provided as argument, ask what they want to build:
-     > "What change do you want to work on? Describe what you want to build or fix."
-   - Derive a kebab-case name from the description.
-
-   WI context is held **in-memory** for this flow — no `context.md` is written.
-
-   **IMPORTANT**: Do NOT proceed without a change name.
-
-2. **Create the change directory**
-
-   Create the directory `aspec/changes/<name>/` in the repository.
-
-   This scaffolds the change at `aspec/changes/<name>/`.
-
-3. **Get the artifact build order**
-
-   ```bash
-   aspec status --change "<name>" --json
-   ```
-
-   Parse the JSON to get:
-
-   - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`)
-   - `artifacts`: list of all artifacts with their status and dependencies
-
-4. **Create artifacts in sequence until apply-ready**
-
-   Use the **TodoWrite tool** to track progress through the artifacts.
-
-   Loop through artifacts in dependency order (artifacts with no pending dependencies first):
-
-   a. **For each artifact that is `ready` (dependencies satisfied)**:
-
-   - Get instructions:
-     ```bash
-     aspec instructions <artifact-id> --change "<name>" --json
-     ```
-   - The instructions JSON includes:
-     - `context`: Project background (constraints for you - do NOT include in output)
-     - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
-     - `template`: The structure to use for your output file
-     - `instruction`: Schema-specific guidance for this artifact type
-     - `outputPath`: Where to write the artifact
-     - `dependencies`: Completed artifacts to read for context
-   - Read any completed dependency files for context
-   - If creating the first artifact (proposal):
-- If WI context is available (in-memory): use WI title/description as the problem statement, acceptance criteria as the requirements basis, and include a `## Related Work Item` section: `**#{id}** — {System.Title} ({WorkItemType}) · Project: {System.TeamProject}`
-    - Create the artifact file using `template` as the structure
-   - Apply `context` and `rules` as constraints - but do NOT copy them into the file
-   - Show brief progress: "✓ Created <artifact-id>"
-
-   b. **Continue until all `applyRequires` artifacts are complete**
-
-   - After creating each artifact, re-run `aspec status --change "<name>" --json`
-   - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array
-   - Stop when all `applyRequires` artifacts are done
-
-   c. **If an artifact requires user input** (unclear context):
-
-   - Use **AskUserQuestion tool** to clarify
-   - Then continue with creation
-
-5. **Show final status**
-   ```bash
-   aspec status --change "<name>"
-   ```
-
-**Output**
-
-After completing all artifacts, summarize:
-
-- Change name and location
-- List of artifacts created with brief descriptions
-- What's ready: "All artifacts created! Ready for implementation."
-- Prompt: "Run `/cleto-apply` to start implementing."
-
-**Artifact Creation Guidelines**
-
-- Follow the `instruction` field from `aspec instructions` for each artifact type
-- The schema defines what each artifact should contain - follow it
-- Read dependency artifacts for context before creating new ones
-- Use `template` as the structure for your output file - fill in its sections
-- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file
-  - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact
-  - These guide what you write, but should never appear in the output
-
-**Guardrails**
-
-- Create ALL artifacts needed for implementation (as defined by schema's `apply.requires`)
-- Always read dependency artifacts before creating a new one
-- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
-- If a change with that name already exists, ask if user wants to continue it or create a new one
-- Verify each artifact file exists after writing before proceeding to next
+Work Item grounding (when the request references a Work Item) is owned by `@context-resolver`.

package/commands/cleto-new.md

@@ -2,114 +2,8 @@
 description: Start a new change using the experimental artifact workflow
 ---
 
-Start a new change using the experimental artifact-driven approach.
+Invoke the `ancleto-new` skill with the Skill tool and follow it exactly; do not improvise steps.
 
 **Input**: The argument after `/cleto-new` is the change name (kebab-case), OR a description of what the user wants to build.
 
-**Steps**
-
-1. **Resolve Work Item context and derive change name**
-
-   Resolve Work Item context in this order — stop at the first source that yields data:
-
-   a. **In-session context** — If WI data was already fetched in this session, use it. Proceed to name derivation below.
-   b. **`context.md`** — If a change name was provided as argument and `aspec/changes/<name>/context.md` exists, read it and use its content. Proceed to name derivation.
-   c. **Ask the user** — Use the **AskUserQuestion tool** to ask for the Work Item reference. Two accepted formats:
-
-   - **ID + Project** — e.g., ID `12345` and project `MyProject`
-   - **Full URL** — e.g., `https://dev.azure.com/org/MyProject/_workitems/edit/12345`
-
-   > "Do you have an Azure DevOps Work Item for this change? Provide the Work Item ID and Azure DevOps project name (e.g., ID: `12345`, Project: `MyProject`), or paste the full Work Item URL. Skip to describe the change manually."
-
-   **If WI provided:**
-
-   - If URL provided: extract numeric ID (pattern: `_workitems/edit/{id}`) AND project name (pattern: `/{org}/{project}/_workitems/`)
-   - Use BOTH `id` AND `project` when calling the AzDO MCP (`wit_get_work_item`) — never call with ID alone
-   - Extract from the response: `System.Id`, `System.Title`, `System.Description`, `Microsoft.VSTS.Common.AcceptanceCriteria`, `System.WorkItemType`
-   - Suggest a kebab-case name derived from `System.Title` (e.g., "Add payment gateway" → `add-payment-gateway`)
-   - Let the user accept or modify the suggested name before proceeding
-
-   **If skipped:**
-
-   - Display: "No work item linked — consider linking one for traceability."
-   - If no change name was provided as argument, ask what they want to build:
-     > "What change do you want to work on? Describe what you want to build or fix."
-   - Derive a kebab-case name from the description.
-
-   **IMPORTANT**: Do NOT proceed without a change name.
-
-2. **Determine the workflow schema**
-
-   Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.
-
-   **Use a different schema only if the user mentions:**
-
-   - A specific schema name → use `--schema <name>`
-   - "show workflows" or "what workflows" → run `aspec schemas --json` and let them choose
-
-   **Otherwise**: Omit `--schema` to use the default.
-
-3. **Create the change directory**
-
-   Create the directory `aspec/changes/<name>/` in the repository.
-
-   Record the schema selection in the change metadata only if the user requested a specific workflow.
-   This scaffolds the change at `aspec/changes/<name>/` with the selected schema.
-
-4. **Persist Work Item context to `context.md`** (only if WI was resolved in step 1)
-
-   Write WI context to `aspec/changes/<name>/context.md`:
-
-   ```
-   # Work Item Context
-
-   **ID**: #{id}
-   **Type**: {WorkItemType}
-   **Title**: {System.Title}
-   **Project**: {System.TeamProject}
-
-   ## Description
-   {System.Description (HTML stripped)}
-
-   ## Acceptance Criteria
-   {Microsoft.VSTS.Common.AcceptanceCriteria (HTML stripped)}
-   ```
-
-   Skip this step if the user skipped the Work Item step.
-
-5. **Show the artifact status**
-
-   ```bash
-   aspec status --change "<name>"
-   ```
-
-   This shows which artifacts need to be created and which are ready (dependencies satisfied).
-
-6. **Get instructions for the first artifact**
-   The first artifact depends on the schema. Check the status output to find the first artifact with status "ready".
-
-   ```bash
-   aspec instructions <first-artifact-id> --change "<name>"
-   ```
-
-   This outputs the template and context for creating the first artifact.
-
-7. **STOP and wait for user direction**
-
-**Output**
-
-After completing the steps, summarize:
-
-- Change name and location
-- Schema/workflow being used and its artifact sequence
-- Current status (0/N artifacts complete)
-- The template for the first artifact
-- Prompt: "Ready to create the first artifact? Run `/cleto-continue` or just describe what this change is about and I'll draft it."
-
-**Guardrails**
-
-- Do NOT create any artifacts yet - just show the instructions
-- Do NOT advance beyond showing the first artifact template
-- If the name is invalid (not kebab-case), ask for a valid name
-- If a change with that name already exists, suggest using `/cleto-continue` instead
-- Pass --schema if using a non-default workflow
+Work Item grounding (when the request references a Work Item) is owned by `@context-resolver`.