@thiagodiogo/pscode 1.0.0

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

@@ -0,0 +1,287 @@
+export function getApplyChangeSkillTemplate() {
+    return {
+        name: 'pscode-apply-change',
+        description: 'Implement tasks from an Pscode change. Use when the user wants to start implementing, continue implementation, or work through tasks.',
+        instructions: getApplyInstructions(),
+        license: 'MIT',
+        compatibility: 'Requires pscode CLI.',
+        metadata: { author: 'pscode', version: '1.0' },
+    };
+}
+export function getPsApplyCommandTemplate() {
+    return {
+        name: 'PS: Apply',
+        description: 'Implement tasks from a Pscode change',
+        category: 'Workflow',
+        tags: ['workflow', 'apply', 'implementation'],
+        content: getApplyInstructions(),
+    };
+}
+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:archive <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:archive\`
+   - 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:archive\`.
+\`\`\`
+
+**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

package/dist/core/templates/workflows/archive-change.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Skill Template Workflow Modules
+ *
+ * This file is generated by splitting the legacy monolithic
+ * templates file into workflow-focused modules.
+ */
+import type { SkillTemplate, CommandTemplate } from '../types.js';
+export declare function getArchiveChangeSkillTemplate(): SkillTemplate;
+export declare function getPsArchiveCommandTemplate(): CommandTemplate;
+//# sourceMappingURL=archive-change.d.ts.map

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

@@ -0,0 +1,227 @@
+export function getArchiveChangeSkillTemplate() {
+    return {
+        name: 'pscode-archive-change',
+        description: 'Archive a completed change. Use when the user wants to finalize and archive a change after implementation is complete.',
+        instructions: getArchiveInstructions(),
+        license: 'MIT',
+        compatibility: 'Requires pscode CLI.',
+        metadata: { author: 'pscode', version: '1.0' },
+    };
+}
+export function getPsArchiveCommandTemplate() {
+    return {
+        name: 'PS: Archive',
+        description: 'Archive a completed change',
+        category: 'Workflow',
+        tags: ['workflow', 'archive'],
+        content: getArchiveInstructions(),
+    };
+}
+function getArchiveInstructions() {
+    return `Archive a completed change.
+
+**Input**: Optionally specify a change name (e.g., \`/ps:archive 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. **If no change name provided, prompt for selection**
+
+   Run \`pscode list --json\` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+   Show only active changes (not already archived).
+   Include the schema used for each change if available.
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+   Run \`pscode status --change "<name>" --json\` to check artifact completion.
+
+   Parse the JSON to understand:
+   - \`schemaName\`: The workflow being used
+   - \`planningHome\`, \`changeRoot\`, \`artifactPaths\`, and \`actionContext\`: path and scope context
+   - \`artifacts\`: List of artifacts with their status (\`done\` or other)
+
+   If status reports \`actionContext.mode: "workspace-planning"\`, explain that workspace archive is not supported in this slice and STOP.
+
+   **If any artifacts are not \`done\`:**
+   - Display warning listing incomplete artifacts
+   - Use **AskUserQuestion tool** to confirm user wants to proceed
+   - Proceed if user confirms
+
+3. **Check task completion status**
+
+   Read the tasks file (typically \`tasks.md\`) to check for incomplete tasks.
+
+   Count tasks marked with \`- [ ]\` (incomplete) vs \`- [x]\` (complete).
+
+   **If incomplete tasks found:**
+   - Display warning showing count of incomplete tasks
+   - Use **AskUserQuestion tool** to confirm user wants to proceed
+   - Proceed if user confirms
+
+   **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+   Use \`artifactPaths.specs.existingOutputPaths\` from status JSON to check for delta specs. If none exist, proceed without sync prompt.
+
+   **If delta specs exist:**
+   - Compare each delta spec with its corresponding main spec at \`pscode/specs/<capability>/spec.md\`
+   - Determine what changes would be applied (adds, modifications, removals, renames)
+   - Show a combined summary before prompting
+
+   **Prompt options:**
+   - If changes needed: "Sync now (recommended)", "Archive without syncing"
+   - If already synced: "Archive now", "Sync anyway", "Cancel"
+
+   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke pscode-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
+
+5. **Perform the archive**
+
+   Create an \`archive\` directory under \`planningHome.changesDir\` if it doesn't exist:
+   \`\`\`bash
+   mkdir -p "<planningHome.changesDir>/archive"
+   \`\`\`
+
+   Generate target name using current date: \`YYYY-MM-DD-<change-name>\`
+
+   **Check if target already exists:**
+   - If yes: Fail with error, suggest renaming existing archive or using different date
+   - If no: Move \`changeRoot\` to the archive directory
+
+   \`\`\`bash
+   mv "<changeRoot>" "<planningHome.changesDir>/archive/YYYY-MM-DD-<name>"
+   \`\`\`
+
+6. **Trello Integration — move card to "Concluído" (optional)**
+
+   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.done\` (and optionally \`lists.testing\`, \`lists.deploy\`, \`lists.developing\`, \`lists.ready\`, \`lists.refining\`, \`lists.backlog\`).
+
+   Search for the change's card across all configured lists in reverse-workflow order:
+   \`deploy\` → \`testing\` → \`developing\` → \`ready\` → \`refining\` → \`backlog\`.
+   Stop as soon as a matching card is found.
+
+   **If \`lists.done\` is configured:**
+   - **Card found:** move it to \`lists.done\` and mark as complete:
+     \`\`\`tool
+     mcp__claude_ai_Trello_Custom__update_card  { card_id: "<id>", list_id: "<lists.done.id>", dueComplete: true }
+     \`\`\`
+   - **No card found:** create one in \`lists.done\`:
+     \`\`\`tool
+     mcp__claude_ai_Trello_Custom__create_card
+       list_id: "<lists.done.id>"
+       name: "<human-readable change name in Portuguese>"
+       desc: "Arquivada via /ps:archive"
+     \`\`\`
+     Then mark it complete.
+
+   Assign 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>" }
+   \`\`\`
+
+   Mark any checklist items as complete:
+   \`\`\`tool
+   mcp__claude_ai_Trello_Custom__get_card_checklists  { card_id: "<cardId>" }
+   \`\`\`
+   For each checklist item not already complete, call:
+   \`\`\`tool
+   mcp__claude_ai_Trello_Custom__update_checkitem  { card_id: "<cardId>", checklist_id: "<clId>", checkitem_id: "<itemId>", state: "complete" }
+   \`\`\`
+
+   Add a completion comment in Portuguese:
+   \`\`\`tool
+   mcp__claude_ai_Trello_Custom__add_comment
+     card_id: "<cardId>"
+     text: |
+       Change arquivada via /ps:archive
+
+       Change: <change-name>
+       Schema: <schema-name>
+       Arquivada em: <archive-path>
+       Specs: <sincronizado / sem delta specs / sync pulado>
+       Tasks: <N>/<N> concluidas
+
+       Fluxo encerrado. Nenhuma acao adicional necessaria.
+   \`\`\`
+
+   If any Trello call fails, continue — Trello is auxiliary, never blocking.
+
+7. **Display summary**
+
+   Show archive completion summary including:
+   - Change name
+   - Schema that was used
+   - Archive location
+   - Spec sync status (synced / sync skipped / no delta specs)
+   - Note about any warnings (incomplete artifacts/tasks)
+   - Trello: mention if card was moved to "Concluído"
+
+**Output On Success**
+
+\`\`\`
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** <archive-path>
+**Specs:** ✓ Synced to main specs
+**Trello:** Card moved to ✅ Concluído    ← only shown if Trello is configured
+
+All artifacts complete. All tasks complete.
+\`\`\`
+
+**Output On Success With Warnings**
+
+\`\`\`
+## Archive Complete (with warnings)
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** <archive-path>
+**Specs:** Sync skipped (user chose to skip)
+**Trello:** Card moved to ✅ Concluído    ← only shown if Trello is configured
+
+**Warnings:**
+- Archived with 2 incomplete artifacts
+- Archived with 3 incomplete tasks
+- Delta spec sync was skipped
+
+Review the archive if this was not intentional.
+\`\`\`
+
+**Output On Error (Archive Exists)**
+
+\`\`\`
+## Archive Failed
+
+**Change:** <change-name>
+**Target:** <archive-path>
+
+Target archive directory already exists.
+
+**Options:**
+1. Rename the existing archive
+2. Delete the existing archive if it's a duplicate
+3. Wait until a different date to archive
+\`\`\`
+
+**Guardrails**
+- Always prompt for change selection if not provided
+- Use artifact graph (pscode status --json) for completion checking
+- Don't block archive on warnings — just inform and confirm
+- Preserve .pscode.yaml when moving to archive (it moves with the directory)
+- Show clear summary of what happened
+- If sync is requested, use pscode-sync-specs approach (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting
+- If Trello tools fail, continue normally — Trello is auxiliary, not blocking
+- All content written to Trello must be in Portuguese
+`;
+}
+//# sourceMappingURL=archive-change.js.map

package/dist/core/templates/workflows/bulk-archive-change.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Skill Template Workflow Modules
+ *
+ * This file is generated by splitting the legacy monolithic
+ * templates file into workflow-focused modules.
+ */
+import type { SkillTemplate, CommandTemplate } from '../types.js';
+export declare function getBulkArchiveChangeSkillTemplate(): SkillTemplate;
+export declare function getPsBulkArchiveCommandTemplate(): CommandTemplate;
+//# sourceMappingURL=bulk-archive-change.d.ts.map