@thiagodiogo/pscode 2.0.0 → 2.0.1

package/dist/core/templates/workflows/apply-change.js

@@ -18,270 +18,270 @@ export function getPsApplyCommandTemplate() {
     };
 }
 function getApplyInstructions() {
-    return `Implement tasks from a Pscode change.
-
-**Input**: Optionally specify a change name (e.g., \`/ps:apply add-auth\`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
-
-**Steps**
-
-1. **Select the change**
-
-   If a name is provided, use it. Otherwise:
-   - Infer from conversation context if the user mentioned a change
-   - Auto-select if only one active change exists
-   - If ambiguous, run \`pscode list --json\` to get available changes and use the **AskUserQuestion tool** to let the user select
-
-   Always announce: "Using change: <name>" and how to override (e.g., \`/ps:apply <other>\`).
-
-2. **Trello Integration — move card to "Em Desenvolvimento" (optional)**
-
-   This is the FIRST action after selecting the change — signal immediately that development has started.
-
-   Use the **Read tool** (NOT a shell command) to read \`pscode/trello.yaml\` from the current working directory.
-   The Read tool is cross-platform and works on Windows, macOS, and Linux — never use \`cat\` or shell commands to read this file.
-   If the Read tool returns an error (file not found), skip all Trello steps.
-
-   Otherwise parse and extract \`boardId\`, \`lists.refining\`, \`lists.ready\`, \`lists.developing\`, and \`lists.testing\`.
-
-   Search for the change's card across configured lists in priority order:
-   \`refining\` → \`ready\` → \`backlog\` (whichever are configured):
-   \`\`\`tool
-   mcp__claude_ai_Trello_Custom__get_cards  { list_id: "<list.id>" }
-   \`\`\`
-   Look for a card matching the change name (case-insensitive, partial match is sufficient).
-
-   **If \`lists.developing\` is configured:**
-   - **Card found:** move it to \`lists.developing\`.
-   - **No card found:** create one directly in \`lists.developing\` with name and desc in Portuguese.
-
-   **If \`lists.developing\` is NOT configured and \`lists.ready\` is configured:**
-   - Move/create in \`lists.ready\`.
-
-   In all cases, assign the current user:
-   \`\`\`tool
-   mcp__claude_ai_Trello_Custom__get_me
-   mcp__claude_ai_Trello_Custom__add_card_member  { card_id: "<cardId>", member_id: "<me.id>" }
-   \`\`\`
-   Save \`cardId\` for the completion step.
-
-   If any Trello call fails, continue — Trello is auxiliary, never blocking.
-
-3. **Check status to understand the schema**
-   \`\`\`bash
-   pscode status --change "<name>" --json
-   \`\`\`
-   Parse the JSON to understand:
-   - \`schemaName\`: The workflow being used (e.g., "spec-driven")
-   - \`planningHome\`, \`changeRoot\`, and \`actionContext\`: planning scope and edit constraints
-   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
-
-4. **Get apply instructions**
-
-   \`\`\`bash
-   pscode instructions apply --change "<name>" --json
-   \`\`\`
-
-   This returns:
-   - \`contextFiles\`: artifact ID -> array of concrete file paths (varies by schema)
-   - Progress (total, complete, remaining)
-   - Task list with status
-   - Dynamic instruction based on current state
-
-   **Handle states:**
-   - If \`state: "blocked"\` (missing artifacts): show message, suggest using \`/ps:continue\`
-   - If \`state: "all_done"\`: congratulate, suggest archive
-   - Otherwise: proceed to implementation
-
-   **Workspace guard:** If status JSON reports \`actionContext.mode: "workspace-planning"\` and \`allowedEditRoots\` is empty, explain that full workspace apply is not supported in this slice. Treat linked repos and folders as read-only context, ask the user to select an affected area, and STOP before editing files.
-
-5. **Read context files**
-
-   Read every file path listed under \`contextFiles\` from the apply instructions output.
-
-6. **Show current progress**
-
-   Display:
-   - Schema being used
-   - Progress: "N/M tasks complete"
-   - Remaining tasks overview
-   - Dynamic instruction from CLI
-
-7. **Implement tasks (loop until done or blocked)**
-
-   For each pending task:
-   - Show which task is being worked on
-   - Make the code changes required
-   - Keep changes minimal and focused
-   - Mark task complete in the tasks file: \`- [ ]\` → \`- [x]\`
-   - Continue to next task
-
-   **Pause if:**
-   - Task is unclear → ask for clarification
-   - Implementation reveals a design issue → suggest updating artifacts
-   - Error or blocker encountered → report and wait for guidance
-   - User interrupts
-
-8. **On completion: move card to "Em Teste" (optional)**
-
-   When all tasks are complete (\`state: "all_done"\`):
-
-   If Trello is configured and \`cardId\` was saved:
-
-   a. If \`lists.testing\` is configured, move the card there:
-      \`\`\`tool
-      mcp__claude_ai_Trello_Custom__update_card  { card_id: "<cardId>", list_id: "<lists.testing.id>" }
-      \`\`\`
-
-   b. Add a comment in Portuguese:
-      \`\`\`tool
-      mcp__claude_ai_Trello_Custom__add_comment
-        card_id: "<cardId>"
-        text: |
-          Implementacao concluida via /ps:apply
-
-          Change: <change-name>
-          Tasks: <N>/<N> concluidas
-
-          Aguardando validacao antes de mover para Ready to Deploy.
-      \`\`\`
-
-   If any Trello call fails, continue — Trello is auxiliary, never blocking.
-
-9. **Fase de Testes — validar implementação**
-
-   After completing all tasks (and moving the card to "Em Teste" if Trello is configured),
-   use the **AskUserQuestion tool** to ask how the user wants to proceed with validation:
-
-   - **"Vou testar eu mesmo"** — user will test independently; wait for them to report back
-   - **"Quero que você teste"** — Claude should invoke the \`verify\` skill to validate the implementation
-   - **"Já testei, está funcionando"** — user already confirmed; proceed to move card to "Ready to Deploy"
-
-   **If user chooses "Vou testar eu mesmo":**
-   - Tell them to test and come back when ready (e.g., saying "está funcionando" or "encontrei um problema")
-   - Wait — do NOT proceed until the user responds
-
-   **If user chooses to have Claude test:**
-   - Use the **Skill tool** to invoke the \`verify\` skill, which runs the app and observes the change
-   - Report the findings clearly to the user
-   - Ask: "A implementação está funcionando como esperado?" (Sim / Não, encontrei um problema)
-
-   **When the user confirms it's working** (any path above):
-
-   If Trello is configured, \`cardId\` was saved, and \`lists.deploy\` is configured:
-   a. Move the card to "Ready to Deploy":
-      \`\`\`tool
-      mcp__claude_ai_Trello_Custom__update_card  { card_id: "<cardId>", list_id: "<lists.deploy.id>" }
-      \`\`\`
-   b. Add a comment in Portuguese:
-      \`\`\`tool
-      mcp__claude_ai_Trello_Custom__add_comment
-        card_id: "<cardId>"
-        text: |
-          Implementacao validada e aprovada para deploy.
-
-          Testado por: <usuario / Claude>
-          Status: Funcionando
-
-          Proximo passo: /ps:complete <name> para arquivar a change.
-      \`\`\`
-
-   If any Trello call fails, continue — Trello is auxiliary, never blocking.
-
-   **If user reports a problem:**
-   - Acknowledge the issue and ask for details
-   - Resume implementation to fix the problem (loop back to step 7)
-   - Do NOT move the card to "Ready to Deploy" until the user confirms it's working
-
-10. **On completion or pause, show status**
-
-   Display:
-   - Tasks completed this session
-   - Overall progress: "N/M tasks complete"
-   - If all done and approved: mention Trello stage (Em Teste or Ready to Deploy) and suggest \`/ps:complete\`
-   - If paused: explain why and wait for guidance
-
-**Output During Implementation**
-
-\`\`\`
-## Implementing: <change-name> (schema: <schema-name>)
-
-Working on task 3/7: <task description>
-[...implementation happening...]
-✓ Task complete
-
-Working on task 4/7: <task description>
-[...implementation happening...]
-✓ Task complete
-\`\`\`
-
-**Output On Completion (aguardando testes)**
-
-\`\`\`
-## Implementation Complete
-
-**Change:** <change-name>
-**Schema:** <schema-name>
-**Progress:** 7/7 tasks complete ✓
-**Trello:** Card moved to 🧪 Em Teste        ← only shown if Trello is configured
-
-### Completed This Session
-- [x] Task 1
-- [x] Task 2
-...
-
-All tasks complete! How would you like to validate the implementation?
-\`\`\`
-
-**Output After Validation Approved**
-
-\`\`\`
-## Validation Approved ✅
-
-**Change:** <change-name>
-**Trello:** Card moved to 🚀 Ready to Deploy  ← only shown if lists.deploy is configured
-
-Ready to archive with \`/ps:complete\`.
-\`\`\`
-
-**Output On Pause (Issue Encountered)**
-
-\`\`\`
-## Implementation Paused
-
-**Change:** <change-name>
-**Schema:** <schema-name>
-**Progress:** 4/7 tasks complete
-
-### Issue Encountered
-<description of the issue>
-
-**Options:**
-1. <option 1>
-2. <option 2>
-3. Other approach
-
-What would you like to do?
-\`\`\`
-
-**Guardrails**
-- Keep going through tasks until done or blocked
-- Always read context files before starting
-- If task is ambiguous, pause and ask before implementing
-- If implementation reveals issues, pause and suggest artifact updates
-- Keep code changes minimal and scoped to each task
-- Update task checkbox immediately after completing each task
-- Pause on errors, blockers, or unclear requirements — don't guess
-- Use contextFiles from CLI output, don't assume specific file names
-- If Trello tools fail, continue normally — Trello is auxiliary, not blocking
-- All content written to Trello must be in Portuguese
-- Never move the card to "Ready to Deploy" without explicit user confirmation that the implementation is working
-- If the user reports a problem during testing, loop back to fix before asking again
-- Offer to invoke the \`verify\` skill when the user wants Claude to test — don't skip straight to archive
-
-**Fluid Workflow Integration**
-
-- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation
-- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts
+    return `Implement tasks from a Pscode change.
+
+**Input**: Optionally specify a change name (e.g., \`/ps:apply add-auth\`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+   If a name is provided, use it. Otherwise:
+   - Infer from conversation context if the user mentioned a change
+   - Auto-select if only one active change exists
+   - If ambiguous, run \`pscode list --json\` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+   Always announce: "Using change: <name>" and how to override (e.g., \`/ps:apply <other>\`).
+
+2. **Trello Integration — move card to "Em Desenvolvimento" (optional)**
+
+   This is the FIRST action after selecting the change — signal immediately that development has started.
+
+   Use the **Read tool** (NOT a shell command) to read \`pscode/trello.yaml\` from the current working directory.
+   The Read tool is cross-platform and works on Windows, macOS, and Linux — never use \`cat\` or shell commands to read this file.
+   If the Read tool returns an error (file not found), skip all Trello steps.
+
+   Otherwise parse and extract \`boardId\`, \`lists.refining\`, \`lists.ready\`, \`lists.developing\`, and \`lists.testing\`.
+
+   Search for the change's card across configured lists in priority order:
+   \`refining\` → \`ready\` → \`backlog\` (whichever are configured):
+   \`\`\`tool
+   mcp__claude_ai_Trello_Custom__get_cards  { list_id: "<list.id>" }
+   \`\`\`
+   Look for a card matching the change name (case-insensitive, partial match is sufficient).
+
+   **If \`lists.developing\` is configured:**
+   - **Card found:** move it to \`lists.developing\`.
+   - **No card found:** create one directly in \`lists.developing\` with name and desc in Portuguese.
+
+   **If \`lists.developing\` is NOT configured and \`lists.ready\` is configured:**
+   - Move/create in \`lists.ready\`.
+
+   In all cases, assign the current user:
+   \`\`\`tool
+   mcp__claude_ai_Trello_Custom__get_me
+   mcp__claude_ai_Trello_Custom__add_card_member  { card_id: "<cardId>", member_id: "<me.id>" }
+   \`\`\`
+   Save \`cardId\` for the completion step.
+
+   If any Trello call fails, continue — Trello is auxiliary, never blocking.
+
+3. **Check status to understand the schema**
+   \`\`\`bash
+   pscode status --change "<name>" --json
+   \`\`\`
+   Parse the JSON to understand:
+   - \`schemaName\`: The workflow being used (e.g., "spec-driven")
+   - \`planningHome\`, \`changeRoot\`, and \`actionContext\`: planning scope and edit constraints
+   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+4. **Get apply instructions**
+
+   \`\`\`bash
+   pscode instructions apply --change "<name>" --json
+   \`\`\`
+
+   This returns:
+   - \`contextFiles\`: artifact ID -> array of concrete file paths (varies by schema)
+   - Progress (total, complete, remaining)
+   - Task list with status
+   - Dynamic instruction based on current state
+
+   **Handle states:**
+   - If \`state: "blocked"\` (missing artifacts): show message, suggest using \`/ps:continue\`
+   - If \`state: "all_done"\`: congratulate, suggest archive
+   - Otherwise: proceed to implementation
+
+   **Workspace guard:** If status JSON reports \`actionContext.mode: "workspace-planning"\` and \`allowedEditRoots\` is empty, explain that full workspace apply is not supported in this slice. Treat linked repos and folders as read-only context, ask the user to select an affected area, and STOP before editing files.
+
+5. **Read context files**
+
+   Read every file path listed under \`contextFiles\` from the apply instructions output.
+
+6. **Show current progress**
+
+   Display:
+   - Schema being used
+   - Progress: "N/M tasks complete"
+   - Remaining tasks overview
+   - Dynamic instruction from CLI
+
+7. **Implement tasks (loop until done or blocked)**
+
+   For each pending task:
+   - Show which task is being worked on
+   - Make the code changes required
+   - Keep changes minimal and focused
+   - Mark task complete in the tasks file: \`- [ ]\` → \`- [x]\`
+   - Continue to next task
+
+   **Pause if:**
+   - Task is unclear → ask for clarification
+   - Implementation reveals a design issue → suggest updating artifacts
+   - Error or blocker encountered → report and wait for guidance
+   - User interrupts
+
+8. **On completion: move card to "Em Teste" (optional)**
+
+   When all tasks are complete (\`state: "all_done"\`):
+
+   If Trello is configured and \`cardId\` was saved:
+
+   a. If \`lists.testing\` is configured, move the card there:
+      \`\`\`tool
+      mcp__claude_ai_Trello_Custom__update_card  { card_id: "<cardId>", list_id: "<lists.testing.id>" }
+      \`\`\`
+
+   b. Add a comment in Portuguese:
+      \`\`\`tool
+      mcp__claude_ai_Trello_Custom__add_comment
+        card_id: "<cardId>"
+        text: |
+          Implementacao concluida via /ps:apply
+
+          Change: <change-name>
+          Tasks: <N>/<N> concluidas
+
+          Aguardando validacao antes de mover para Ready to Deploy.
+      \`\`\`
+
+   If any Trello call fails, continue — Trello is auxiliary, never blocking.
+
+9. **Fase de Testes — validar implementação**
+
+   After completing all tasks (and moving the card to "Em Teste" if Trello is configured),
+   use the **AskUserQuestion tool** to ask how the user wants to proceed with validation:
+
+   - **"Vou testar eu mesmo"** — user will test independently; wait for them to report back
+   - **"Quero que você teste"** — Claude should invoke the \`verify\` skill to validate the implementation
+   - **"Já testei, está funcionando"** — user already confirmed; proceed to move card to "Ready to Deploy"
+
+   **If user chooses "Vou testar eu mesmo":**
+   - Tell them to test and come back when ready (e.g., saying "está funcionando" or "encontrei um problema")
+   - Wait — do NOT proceed until the user responds
+
+   **If user chooses to have Claude test:**
+   - Use the **Skill tool** to invoke the \`verify\` skill, which runs the app and observes the change
+   - Report the findings clearly to the user
+   - Ask: "A implementação está funcionando como esperado?" (Sim / Não, encontrei um problema)
+
+   **When the user confirms it's working** (any path above):
+
+   If Trello is configured, \`cardId\` was saved, and \`lists.deploy\` is configured:
+   a. Move the card to "Ready to Deploy":
+      \`\`\`tool
+      mcp__claude_ai_Trello_Custom__update_card  { card_id: "<cardId>", list_id: "<lists.deploy.id>" }
+      \`\`\`
+   b. Add a comment in Portuguese:
+      \`\`\`tool
+      mcp__claude_ai_Trello_Custom__add_comment
+        card_id: "<cardId>"
+        text: |
+          Implementacao validada e aprovada para deploy.
+
+          Testado por: <usuario / Claude>
+          Status: Funcionando
+
+          Proximo passo: /ps:complete <name> para arquivar a change.
+      \`\`\`
+
+   If any Trello call fails, continue — Trello is auxiliary, never blocking.
+
+   **If user reports a problem:**
+   - Acknowledge the issue and ask for details
+   - Resume implementation to fix the problem (loop back to step 7)
+   - Do NOT move the card to "Ready to Deploy" until the user confirms it's working
+
+10. **On completion or pause, show status**
+
+   Display:
+   - Tasks completed this session
+   - Overall progress: "N/M tasks complete"
+   - If all done and approved: mention Trello stage (Em Teste or Ready to Deploy) and suggest \`/ps:complete\`
+   - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+\`\`\`
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+\`\`\`
+
+**Output On Completion (aguardando testes)**
+
+\`\`\`
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+**Trello:** Card moved to 🧪 Em Teste        ← only shown if Trello is configured
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! How would you like to validate the implementation?
+\`\`\`
+
+**Output After Validation Approved**
+
+\`\`\`
+## Validation Approved ✅
+
+**Change:** <change-name>
+**Trello:** Card moved to 🚀 Ready to Deploy  ← only shown if lists.deploy is configured
+
+Ready to archive with \`/ps:complete\`.
+\`\`\`
+
+**Output On Pause (Issue Encountered)**
+
+\`\`\`
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+\`\`\`
+
+**Guardrails**
+- Keep going through tasks until done or blocked
+- Always read context files before starting
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements — don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+- If Trello tools fail, continue normally — Trello is auxiliary, not blocking
+- All content written to Trello must be in Portuguese
+- Never move the card to "Ready to Deploy" without explicit user confirmation that the implementation is working
+- If the user reports a problem during testing, loop back to fix before asking again
+- Offer to invoke the \`verify\` skill when the user wants Claude to test — don't skip straight to archive
+
+**Fluid Workflow Integration**
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts
 `;
 }
 //# sourceMappingURL=apply-change.js.map