@thiagodiogo/pscode 2.1.0 → 2.2.0

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

@@ -1,9 +1,9 @@
+import { buildNextStepComment } from './trello-next-step-comment.js';
 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' },
     };
@@ -18,6 +18,13 @@ export function getPsApplyCommandTemplate() {
     };
 }
 function getApplyInstructions() {
+    // Pre-filled next-step comment (card title interpolated), shared via the
+    // trello-next-step-comment utility and indented to sit inside the Trello
+    // comment `text: |` block in the testing phase below.
+    const completeNextStep = buildNextStepComment('<card title>', '/ps:complete')
+        .split('\n')
+        .map((line) => (line.length > 0 ? `          ${line}` : ''))
+        .join('\n');
     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.
@@ -94,10 +101,27 @@ function getApplyInstructions() {
 
    **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**
+5. **Read context files and PR config**
 
    Read every file path listed under \`contextFiles\` from the apply instructions output.
 
+   Additionally, use the **Read tool** to read \`pscode/config.yaml\` from the current working directory.
+
+   **If \`pscode/config.yaml\` exists and \`pr.enabled: true\`:**
+
+   Before starting any implementation, inform the user of the PR workflow requirements:
+
+   > 🔀 **Workflow de PR ativo** — este projeto requer branches dedicadas e Pull Requests.
+   > - Branch: crie uma branch com o padrão \`<pr.branch.pattern>\` antes de codificar
+   > - Título do PR: \`<pr.title.template>\`
+   > - Descrição do PR: use o template definido em \`pr.description.template\`
+   > - Ao abrir o PR: \`<"comente o link do PR nesta task" se pr.comments.linkInTask: true, senão omita>\`
+
+   The agent MUST create the branch with the configured pattern before making any code changes.
+   Template variables available: \`{change-name}\` = current change name, \`{type}\` = feat/fix/chore, \`{ticket}\` = ticket ID if available.
+
+   **If \`pscode/config.yaml\` does not exist, or \`pr.enabled: false\`, or file not found:** continue normally without any PR instructions.
+
 6. **Show current progress**
 
    Display:
@@ -182,7 +206,7 @@ function getApplyInstructions() {
           Testado por: <usuario / Claude>
           Status: Funcionando
 
-          Proximo passo: /ps:complete <name> para arquivar a change.
+${completeNextStep}
       \`\`\`
 
    If any Trello call fails, continue — Trello is auxiliary, never blocking.

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

@@ -3,7 +3,6 @@ export function getCompleteChangeSkillTemplate() {
         name: 'pscode-archive-change',
         description: 'Complete a completed change. Use when the user wants to finalize and complete a change after implementation is complete.',
         instructions: getArchiveInstructions(),
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };

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

@@ -239,7 +239,6 @@ No active changes found. Create a new change to get started.
 - Preserve .pscode.yaml when moving to archive
 - Archive directory target uses current date: YYYY-MM-DD-<name>
 - If archive target exists, fail that change but continue with others`,
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };

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

@@ -110,7 +110,6 @@ For other schemas, follow the \`instruction\` field from the CLI output.
 - **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`,
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };

package/dist/core/templates/workflows/explore.js

@@ -426,7 +426,6 @@ Do NOT move the card. End the loop.
 - **Do question assumptions** - Including the user's and your own
 - **Always run the refinement loop after propose** - When exploration leads to a proposal, the refinement validation loop (Steps RF1–RF3) is mandatory, not optional
 - **Preserve the loop** - Do not exit until the user explicitly approves or cancels`,
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };

package/dist/core/templates/workflows/feedback.js

@@ -100,7 +100,6 @@ Does this look good? I can modify it if you'd like, or submit it as-is.
 \`\`\`
 
 Only proceed with submission after user confirms.`,
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };

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

@@ -93,7 +93,6 @@ After completing all artifacts, summarize:
 - If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
 - If a change with that name already exists, suggest continuing that change instead
 - Verify each artifact file exists after writing before proceeding to next`,
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };

package/dist/core/templates/workflows/handoff.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Handoff Skill / Command Template
+ *
+ * Compacts the current conversation into a handoff document so a fresh agent
+ * (or the same user in a new session) can continue the work seamlessly.
+ */
+import type { SkillTemplate, CommandTemplate } from '../types.js';
+export declare function getHandoffSkillTemplate(): SkillTemplate;
+export declare function getHandoffCommandTemplate(): CommandTemplate;
+//# sourceMappingURL=handoff.d.ts.map

package/dist/core/templates/workflows/handoff.js

@@ -0,0 +1,31 @@
+export function getHandoffSkillTemplate() {
+    return {
+        name: 'pscode-handoff',
+        description: 'Compact the current conversation into a handoff document for another agent to pick up. Use when the user wants to hand off work to a new session or agent.',
+        instructions: getHandoffInstructions(),
+        compatibility: 'Works with any pscode project.',
+        metadata: { author: 'pscode', version: '1.0' },
+    };
+}
+function getHandoffInstructions() {
+    return `Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS — not the current workspace.
+
+Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
+
+Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs, pscode change files). Reference them by path or URL instead.
+
+Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
+
+If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
+`;
+}
+export function getHandoffCommandTemplate() {
+    return {
+        name: 'PS: Handoff',
+        description: 'Compact the current conversation into a handoff document for another agent to pick up',
+        category: 'Workflow',
+        tags: ['handoff', 'sessao', 'continuacao', 'workflow'],
+        content: getHandoffInstructions(),
+    };
+}
+//# sourceMappingURL=handoff.js.map

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

@@ -65,7 +65,6 @@ After completing the steps, summarize:
 - If the name is invalid (not kebab-case), ask for a valid name
 - If a change with that name already exists, suggest continuing that change instead
 - Pass --schema if using a non-default workflow`,
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };

package/dist/core/templates/workflows/onboard.js

@@ -3,7 +3,6 @@ export function getOnboardSkillTemplate() {
         name: 'pscode-onboard',
         description: 'Guided onboarding for Pscode - walk through a complete workflow cycle with narration and real codebase work.',
         instructions: getOnboardInstructions(),
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };

package/dist/core/templates/workflows/propose.js

@@ -1,9 +1,9 @@
+import { buildNextStepComment } from './trello-next-step-comment.js';
 export function getProposeSkillTemplate() {
     return {
         name: 'pscode-propose',
         description: 'Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.',
         instructions: getProposeInstructions(),
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };
@@ -18,6 +18,13 @@ export function getPsProposeCommandTemplate() {
     };
 }
 function getProposeInstructions() {
+    // Pre-filled next-step comment (card title interpolated), shared via the
+    // trello-next-step-comment utility and indented to sit inside the Trello
+    // comment `text: |` blocks below.
+    const applyNextStep = buildNextStepComment('<card title>', '/ps:apply')
+        .split('\n')
+        .map((line) => (line.length > 0 ? `       ${line}` : ''))
+        .join('\n');
     return `Propose a new change - create the change and generate all artifacts in one step.
 
 I'll create a change with artifacts:
@@ -25,7 +32,7 @@ I'll create a change with artifacts:
 - design.md (how)
 - tasks.md (implementation steps)
 
-After artifacts are created, a **refinement validation loop** runs: the user reviews the plan, gives feedback, and when satisfied the Trello card is moved to Ready to Dev.
+After artifacts are created, a **refinement validation loop** runs: the Trello card is updated with the refined plan, the user reviews it, gives feedback, and when satisfied the card is moved to Ready to Dev.
 
 When ready to implement, run /ps:apply
 
@@ -203,22 +210,10 @@ Para iniciar a implementação quando aprovado:
 
 ---
 
-### Step R2 — Ask for user approval
-
-Use **AskUserQuestion** to ask:
-
-> "A implementação e o planejamento estão de acordo com o esperado?"
+### Step R1b — Update Trello card (before asking for approval)
 
-Options:
-- ✅ Sim, está refinada — mover para Ready to Dev
-- 🔄 Não, quero ajustar o plano
-- ❌ Cancelar (manter em refinamento)
-
-**Do NOT update the Trello card description or add any comment before the user approves.**
-
----
-
-### Step R2a — If APPROVED (Sim, está refinada)
+So the user can use the Trello card itself as a visual reference when deciding,
+update the card with the refinement content **before** asking for approval.
 
 1. **Update Trello card description** (if \`cardId\` exists):
    Build the description from the artifacts already read in Step R1:
@@ -237,7 +232,7 @@ Options:
        **Artefatos:** pscode/changes/<name>/
    \`\`\`
 
-2. **Add a comment** in Portuguese (if \`cardId\` exists):
+2. **Add a refinement comment** in Portuguese (if \`cardId\` exists):
    \`\`\`tool
    mcp__claude_ai_Trello_Custom__add_comment
      card_id: "<cardId>"
@@ -250,22 +245,44 @@ Options:
        ### Resumo
        <2-3 line summary of what will be built>
 
-       ### Para iniciar a implementação
-       \`\`\`
-       /ps:apply <name>
-       \`\`\`
+${applyNextStep}
 
        _Aguardando aprovação para mover para Ready to Dev._
    \`\`\`
 
-3. **Move the Trello card to the ready list** (if \`lists.ready\` is configured and \`cardId\` exists):
+If any Trello call fails, continue — Trello is auxiliary, never blocking.
+
+---
+
+### Step R2 — Ask for user approval
+
+Use **AskUserQuestion** to ask:
+
+> "A implementação e o planejamento estão de acordo com o esperado?"
+
+Options:
+- ✅ Sim, está refinada — mover para Ready to Dev
+- 🔄 Não, quero ajustar o plano
+- ❌ Cancelar (manter em refinamento)
+
+At this point the Trello card already reflects the current refinement (Step R1b),
+so the user can review it before deciding.
+
+---
+
+### Step R2a — If APPROVED (Sim, está refinada)
+
+The card description and refinement comment were already added in Step R1b.
+Now just move the card and register the explicit approval.
+
+1. **Move the Trello card to the ready list** (if \`lists.ready\` is configured and \`cardId\` exists):
    \`\`\`tool
    mcp__claude_ai_Trello_Custom__update_card
      card_id: "<cardId>"
      list_id: "<lists.ready.id>"
    \`\`\`
 
-4. **Add a final Trello comment** (if cardId exists):
+2. **Add a final Trello comment** (if cardId exists):
    \`\`\`tool
    mcp__claude_ai_Trello_Custom__add_comment
      card_id: "<cardId>"
@@ -274,13 +291,10 @@ Options:
 
        O planejamento foi revisado e aprovado.
 
-       ### Próximo passo
-       \`\`\`
-       /ps:apply <name>
-       \`\`\`
+${applyNextStep}
    \`\`\`
 
-5. **Show success message:**
+3. **Show success message:**
    \`\`\`markdown
    ## ✅ Pronto para desenvolvimento!
 
@@ -305,9 +319,9 @@ Options:
    - Changes to technical approach → update \`design.md\`
    - Changes to tasks → update \`tasks.md\`
 
-3. **Go back to Step R1** and show the updated refinement summary.
+3. **Go back to Step R1** and show the updated refinement summary, then **re-run Step R1b**
+   so the Trello card description and comment reflect the adjusted plan before asking again.
    Keep looping until the user approves or cancels.
-   **Do NOT update the Trello description or add comments until the user approves.**
 
 ---
 

package/dist/core/templates/workflows/trello-draft.js

@@ -1,9 +1,9 @@
+import { getNextStepCommentInstructionBlock } from './trello-next-step-comment.js';
 export function getTrelloDraftSkillTemplate() {
     return {
         name: 'pscode-trello-draft',
         description: 'Capture a raw idea or concept into the Backlog Trello list. Use when the user wants to quickly record something without refining it into a task yet.',
         instructions: getTrelloDraftInstructions(),
-        license: 'MIT',
         compatibility: 'Requires pscode CLI and Trello MCP server configured via /ps:trello-setup.',
         metadata: { author: 'pscode', version: '1.0' },
     };
@@ -141,22 +141,10 @@ Save the returned card \`id\` as \`cardId\` and \`url\` as \`cardUrl\`.
 ## Step 7 — Add next-step comment
 
 Add a comment to the card with the command to take this task to the next stage,
-formatted in Markdown so it is easy to copy and paste.
+with the card title (\`<title>\` from Step 3) pre-filled as the quoted argument so
+it is ready to copy and paste.
 
-\`\`\`tool
-mcp__claude_ai_Trello_Custom__add_comment
-  card_id: "<cardId>"
-  text: |
-    ## Próximo passo
-
-    Para refinar e gerar os artefatos da change, rode:
-
-    \`\`\`
-    /ps:propose
-    \`\`\`
-\`\`\`
-
-If this call fails, log the error and continue — the comment is auxiliary, never blocking.
+${getNextStepCommentInstructionBlock('<title>', '/ps:propose')}
 
 ---
 

package/dist/core/templates/workflows/trello-next-step-comment.d.ts

@@ -1,26 +1,33 @@
 /**
  * Trello Next-Step Comment Utility
  *
- * Builds and posts a Trello comment at the end of each workflow step,
- * showing the exact command (with card title pre-filled) to advance
- * to the next stage.
+ * Builds the Trello comment posted at the end of each workflow step, showing
+ * the exact command (with the card title pre-filled as a quoted argument) to
+ * advance to the next stage — so the dev can copy/paste without typing the name.
  *
- * Usage: import buildNextStepComment and call it with the current stage
- * and card title. Post the result via mcp__claude_ai_Trello_Custom__add_comment.
+ * Pure functions, no side effects and no Trello API calls: the card title is
+ * already available in each skill's flow. Shared across the ps:draft, ps:propose
+ * and ps:apply skill templates to avoid drift in the comment format.
  */
-export type WorkflowStage = 'draft' | 'explore' | 'propose' | 'apply';
 /**
- * Returns the markdown text for the next-step comment.
- * Paste this into mcp__claude_ai_Trello_Custom__add_comment as `text`.
+ * Returns the Markdown text for the next-step comment: a header, a description
+ * line, and a code block with the command and pre-filled, quoted card title.
+ * Paste the result into mcp__claude_ai_Trello_Custom__add_comment as `text`.
+ *
+ * @param cardName          The card title to interpolate as the argument.
+ * @param nextCommand       The command to advance the workflow (e.g. "/ps:apply").
+ * @param fallbackChangeName Optional kebab-case change name used when `cardName`
+ *                           is null, undefined or empty.
  */
-export declare function buildNextStepComment(stage: WorkflowStage, cardTitle: string): string;
+export declare function buildNextStepComment(cardName: string, nextCommand: string, fallbackChangeName?: string): string;
 /**
- * Returns the instruction block to be embedded inside a workflow template.
- * Tells the AI agent how and when to post the next-step comment.
+ * Returns the instruction block embedded inside a workflow skill template. It
+ * tells the AI agent to post a next-step comment built via `buildNextStepComment`,
+ * with the card title pre-filled as the command argument.
  *
- * @param stage   The current workflow stage (determines which command appears)
- * @param titleVar The template variable name that holds the card title at runtime
- *                 (e.g. "<title>", "<cardTitle>"). Default: "<title>"
+ * @param cardName    Placeholder (or literal) card title shown in the generated
+ *                    command (e.g. "<título do card>").
+ * @param nextCommand The command to advance the workflow (e.g. "/ps:apply").
  */
-export declare function getNextStepCommentInstructionBlock(stage: WorkflowStage, titleVar?: string): string;
+export declare function getNextStepCommentInstructionBlock(cardName: string, nextCommand: string): string;
 //# sourceMappingURL=trello-next-step-comment.d.ts.map

package/dist/core/templates/workflows/trello-next-step-comment.js

@@ -1,56 +1,94 @@
 /**
  * Trello Next-Step Comment Utility
  *
- * Builds and posts a Trello comment at the end of each workflow step,
- * showing the exact command (with card title pre-filled) to advance
- * to the next stage.
+ * Builds the Trello comment posted at the end of each workflow step, showing
+ * the exact command (with the card title pre-filled as a quoted argument) to
+ * advance to the next stage — so the dev can copy/paste without typing the name.
  *
- * Usage: import buildNextStepComment and call it with the current stage
- * and card title. Post the result via mcp__claude_ai_Trello_Custom__add_comment.
+ * Pure functions, no side effects and no Trello API calls: the card title is
+ * already available in each skill's flow. Shared across the ps:draft, ps:propose
+ * and ps:apply skill templates to avoid drift in the comment format.
  */
-const NEXT_STEP = {
-    draft: { command: 'ps:propose', label: 'Refinar e gerar os artefatos da change' },
-    explore: { command: 'ps:propose', label: 'Propor a change com todos os artefatos' },
-    propose: { command: 'ps:apply', label: 'Implementar as tasks da change' },
-    apply: { command: 'ps:complete', label: 'Finalizar e sincronizar a change' },
+/** Human-readable label describing what the next command does. */
+const NEXT_STEP_LABELS = {
+    '/ps:propose': 'Para refinar e gerar os artefatos da change',
+    '/ps:apply': 'Para implementar as tasks da change',
+    '/ps:complete': 'Para finalizar e arquivar a change',
 };
+/** Normalizes a command so it always starts with a single leading slash. */
+function normalizeCommand(nextCommand) {
+    const trimmed = (nextCommand ?? '').trim();
+    if (trimmed.length === 0)
+        return '';
+    return trimmed.startsWith('/') ? trimmed : `/${trimmed}`;
+}
+/** Converts an arbitrary string into a kebab-case identifier. */
+function toKebabCase(value) {
+    return (value ?? '')
+        .normalize('NFD')
+        .replace(/[̀-ͯ]/g, '')
+        .trim()
+        .toLowerCase()
+        .replace(/[^a-z0-9]+/g, '-')
+        .replace(/^-+|-+$/g, '');
+}
+/**
+ * Resolves the argument placed after the command. Uses the card title when
+ * available, otherwise falls back to the kebab-case change identifier. Internal
+ * double quotes are escaped so the generated command stays valid.
+ */
+function resolveArgument(cardName, fallbackChangeName) {
+    const name = (cardName ?? '').trim();
+    const resolved = name.length > 0 ? name : toKebabCase(fallbackChangeName) || 'nova-change';
+    return resolved.replace(/"/g, '\\"');
+}
 /**
- * Returns the markdown text for the next-step comment.
- * Paste this into mcp__claude_ai_Trello_Custom__add_comment as `text`.
+ * Returns the Markdown text for the next-step comment: a header, a description
+ * line, and a code block with the command and pre-filled, quoted card title.
+ * Paste the result into mcp__claude_ai_Trello_Custom__add_comment as `text`.
+ *
+ * @param cardName          The card title to interpolate as the argument.
+ * @param nextCommand       The command to advance the workflow (e.g. "/ps:apply").
+ * @param fallbackChangeName Optional kebab-case change name used when `cardName`
+ *                           is null, undefined or empty.
  */
-export function buildNextStepComment(stage, cardTitle) {
-    const next = NEXT_STEP[stage];
-    const escapedTitle = cardTitle.replace(/"/g, '\\"');
-    return `**Avançar etapa:** ${next.label}
+export function buildNextStepComment(cardName, nextCommand, fallbackChangeName = '') {
+    const command = normalizeCommand(nextCommand);
+    const label = NEXT_STEP_LABELS[command] ?? 'Para avançar para a próxima etapa';
+    const argument = resolveArgument(cardName, fallbackChangeName);
+    return `## Próximo passo
+
+${label}, rode:
 
 \`\`\`
-/${next.command} "${escapedTitle}"
+${command} "${argument}"
 \`\`\``;
 }
 /**
- * Returns the instruction block to be embedded inside a workflow template.
- * Tells the AI agent how and when to post the next-step comment.
+ * Returns the instruction block embedded inside a workflow skill template. It
+ * tells the AI agent to post a next-step comment built via `buildNextStepComment`,
+ * with the card title pre-filled as the command argument.
  *
- * @param stage   The current workflow stage (determines which command appears)
- * @param titleVar The template variable name that holds the card title at runtime
- *                 (e.g. "<title>", "<cardTitle>"). Default: "<title>"
+ * @param cardName    Placeholder (or literal) card title shown in the generated
+ *                    command (e.g. "<título do card>").
+ * @param nextCommand The command to advance the workflow (e.g. "/ps:apply").
  */
-export function getNextStepCommentInstructionBlock(stage, titleVar = '<title>') {
-    const next = NEXT_STEP[stage];
-    const escapedTitleVar = titleVar.replace(/"/g, '\\"');
+export function getNextStepCommentInstructionBlock(cardName, nextCommand) {
+    const comment = buildNextStepComment(cardName, nextCommand);
+    const indented = comment
+        .split('\n')
+        .map((line) => (line.length > 0 ? `    ${line}` : ''))
+        .join('\n');
     return `## Step — Add next-step comment
 
-Post a comment on the card so the team always has the ready-to-paste command for the next stage.
+Post a comment on the card with the ready-to-paste command for the next stage,
+using \`buildNextStepComment\` so the card title is pre-filled as the quoted argument:
 
 \`\`\`tool
 mcp__claude_ai_Trello_Custom__add_comment
   card_id: "<cardId>"
   text: |
-    **Avançar etapa:** ${next.label}
-
-    \`\`\`
-    /${next.command} "${escapedTitleVar}"
-    \`\`\`
+${indented}
 \`\`\`
 
 If this call fails, log the error and continue — the comment is auxiliary, never blocking.`;

package/dist/core/templates/workflows/trello-setup.js

@@ -3,7 +3,6 @@ export function getTrelloSetupSkillTemplate() {
         name: 'pscode-trello-setup',
         description: 'Configure Trello integration for your Pscode workflow. Checks MCP availability, reads or creates a Trello board, and writes pscode/trello.yaml with your stage-to-list mapping.',
         instructions: getTrelloSetupInstructions(),
-        license: 'MIT',
         compatibility: 'Requires pscode CLI and the Trello MCP server.',
         metadata: { author: 'pscode', version: '1.0' },
     };

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

@@ -162,7 +162,6 @@ Use clear markdown with:
 - Code references in format: \`file.ts:123\`
 - Specific, actionable recommendations
 - No vague suggestions like "consider reviewing"`,
-        license: 'MIT',
         compatibility: 'Requires pscode CLI.',
         metadata: { author: 'pscode', version: '1.0' },
     };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thiagodiogo/pscode",
-  "version": "2.1.0",
+  "version": "2.2.0",
   "description": "AI-native system for spec-driven development",
   "keywords": [
     "pscode",

package/pscode/content/dixi/commands/ps/apply.md

@@ -0,0 +1,15 @@
+---
+name: "PS: Apply (Dixi)"
+description: Implement tasks with Dixi stack-aware context
+category: Workflow
+tags: [workflow, apply, dixi]
+---
+
+Implement tasks with Dixi architectural awareness.
+
+**Dixi preamble** (execute before starting implementation):
+1. Read `.pscode-dixi.yaml` (if present) to identify `stack` and `family`.
+2. Read `pastelsdd/context/architecture.md` (if present) to load architectural constraints — use them as guardrails during implementation.
+3. Read `pastelsdd/context/testing.md` (if present) to load testing conventions.
+
+Then execute the standard `pscode-apply-change` skill instructions in full.

package/pscode/content/dixi/commands/ps/archive.md

@@ -0,0 +1,14 @@
+---
+name: "PS: Archive (Dixi)"
+description: Complete a change with Dixi stack-aware context
+category: Workflow
+tags: [workflow, archive, dixi]
+---
+
+Complete and archive a change with Dixi awareness.
+
+**Dixi preamble** (execute before archiving):
+1. Read `.pscode-dixi.yaml` (if present) to identify `stack` and `family`.
+2. Run `/pstld:dod` (or prompt the user to run it) to verify the Definition of Done before archiving.
+
+Then execute the standard `pscode-archive-change` skill instructions in full.

package/pscode/content/dixi/commands/ps/complete.md

@@ -0,0 +1,14 @@
+---
+name: "PS: Complete (Dixi)"
+description: Complete a change with Dixi DoD verification
+category: Workflow
+tags: [workflow, complete, dixi]
+---
+
+Complete a change with Dixi awareness.
+
+**Dixi preamble** (execute before archiving):
+1. Read `.pscode-dixi.yaml` (if present) to identify `stack` and `family`.
+2. Read `pastelsdd/context/dod.md` (if present) and verify the Definition of Done before proceeding. If DoD criteria are not met, warn the user and ask whether to continue.
+
+Then execute the standard `pscode-archive-change` skill instructions in full.

package/pscode/content/dixi/commands/ps/draft.md

@@ -0,0 +1,15 @@
+---
+name: "PS: Draft (Dixi)"
+description: "Capture a raw idea into the Backlog Trello list — frictionless, no refinement required"
+category: Workflow
+tags: [trello, draft, ideias, backlog, workflow, dixi]
+---
+
+Capture uma ideia ou conceito bruto diretamente no Backlog do Trello.
+
+**Input**: Texto após `/ps:draft` é a descrição da ideia (pode ser bem rascunho — palavras soltas, fragmentos, intuições vagas).
+Se omitido, perguntar ao usuário.
+
+Este comando é intencionalmente sem atrito. Diferente de `/ps:propose`, faz estruturação mínima — o objetivo é velocidade de captura, não clareza.
+
+Then execute the standard `pscode-trello-draft` skill instructions in full.