@thiagodiogo/pscode 1.0.0

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

@@ -0,0 +1,338 @@
+export function getVerifyChangeSkillTemplate() {
+    return {
+        name: 'pscode-verify-change',
+        description: 'Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.',
+        instructions: `Verify that an implementation matches the change artifacts (specs, tasks, design).
+
+**Input**: Optionally specify a change name. 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 changes that have implementation tasks (tasks artifact exists).
+   Include the schema used for each change if available.
+   Mark changes with incomplete tasks as "(In Progress)".
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **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\`, \`artifactPaths\`, and \`actionContext\`: path and scope context
+   - Which artifacts exist for this change
+
+   If status reports \`actionContext.mode: "workspace-planning"\`, explain that full workspace implementation verification is not supported in this slice and STOP. Do not infer repo-local implementation ownership or edit linked repos.
+
+3. **Get planning context and load artifacts**
+
+   \`\`\`bash
+   pscode instructions apply --change "<name>" --json
+   \`\`\`
+
+   This returns the change directory and \`contextFiles\` (artifact ID -> array of concrete file paths). Read all available artifacts from \`contextFiles\`.
+
+4. **Initialize verification report structure**
+
+   Create a report structure with three dimensions:
+   - **Completeness**: Track tasks and spec coverage
+   - **Correctness**: Track requirement implementation and scenario coverage
+   - **Coherence**: Track design adherence and pattern consistency
+
+   Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
+
+5. **Verify Completeness**
+
+   **Task Completion**:
+   - If \`contextFiles.tasks\` exists, read every file path in it
+   - Parse checkboxes: \`- [ ]\` (incomplete) vs \`- [x]\` (complete)
+   - Count complete vs total tasks
+   - If incomplete tasks exist:
+     - Add CRITICAL issue for each incomplete task
+     - Recommendation: "Complete task: <description>" or "Mark as done if already implemented"
+
+   **Spec Coverage**:
+   - If delta specs exist in \`contextFiles.specs\`:
+     - Extract all requirements (marked with "### Requirement:")
+     - For each requirement:
+       - Search codebase for keywords related to the requirement
+       - Assess if implementation likely exists
+     - If requirements appear unimplemented:
+       - Add CRITICAL issue: "Requirement not found: <requirement name>"
+       - Recommendation: "Implement requirement X: <description>"
+
+6. **Verify Correctness**
+
+   **Requirement Implementation Mapping**:
+   - For each requirement from delta specs:
+     - Search codebase for implementation evidence
+     - If found, note file paths and line ranges
+     - Assess if implementation matches requirement intent
+     - If divergence detected:
+       - Add WARNING: "Implementation may diverge from spec: <details>"
+       - Recommendation: "Review <file>:<lines> against requirement X"
+
+   **Scenario Coverage**:
+   - For each scenario in delta specs (marked with "#### Scenario:"):
+     - Check if conditions are handled in code
+     - Check if tests exist covering the scenario
+     - If scenario appears uncovered:
+       - Add WARNING: "Scenario not covered: <scenario name>"
+       - Recommendation: "Add test or implementation for scenario: <description>"
+
+7. **Verify Coherence**
+
+   **Design Adherence**:
+   - If \`contextFiles.design\` exists:
+     - Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
+     - Verify implementation follows those decisions
+     - If contradiction detected:
+       - Add WARNING: "Design decision not followed: <decision>"
+       - Recommendation: "Update implementation or revise design.md to match reality"
+   - If no design.md: Skip design adherence check, note "No design.md to verify against"
+
+   **Code Pattern Consistency**:
+   - Review new code for consistency with project patterns
+   - Check file naming, directory structure, coding style
+   - If significant deviations found:
+     - Add SUGGESTION: "Code pattern deviation: <details>"
+     - Recommendation: "Consider following project pattern: <example>"
+
+8. **Generate Verification Report**
+
+   **Summary Scorecard**:
+   \`\`\`
+   ## Verification Report: <change-name>
+
+   ### Summary
+   | Dimension    | Status           |
+   |--------------|------------------|
+   | Completeness | X/Y tasks, N reqs|
+   | Correctness  | M/N reqs covered |
+   | Coherence    | Followed/Issues  |
+   \`\`\`
+
+   **Issues by Priority**:
+
+   1. **CRITICAL** (Must fix before archive):
+      - Incomplete tasks
+      - Missing requirement implementations
+      - Each with specific, actionable recommendation
+
+   2. **WARNING** (Should fix):
+      - Spec/design divergences
+      - Missing scenario coverage
+      - Each with specific recommendation
+
+   3. **SUGGESTION** (Nice to fix):
+      - Pattern inconsistencies
+      - Minor improvements
+      - Each with specific recommendation
+
+   **Final Assessment**:
+   - If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
+   - If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
+   - If all clear: "All checks passed. Ready for archive."
+
+**Verification Heuristics**
+
+- **Completeness**: Focus on objective checklist items (checkboxes, requirements list)
+- **Correctness**: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
+- **Coherence**: Look for glaring inconsistencies, don't nitpick style
+- **False Positives**: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
+- **Actionability**: Every issue must have a specific recommendation with file/line references where applicable
+
+**Graceful Degradation**
+
+- If only tasks.md exists: verify task completion only, skip spec/design checks
+- If tasks + specs exist: verify completeness and correctness, skip design
+- If full artifacts: verify all three dimensions
+- Always note which checks were skipped and why
+
+**Output Format**
+
+Use clear markdown with:
+- Table for summary scorecard
+- Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
+- 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' },
+    };
+}
+export function getPsVerifyCommandTemplate() {
+    return {
+        name: 'PS: Verify',
+        description: 'Verify implementation matches change artifacts before archiving',
+        category: 'Workflow',
+        tags: ['workflow', 'verify', 'experimental'],
+        content: `Verify that an implementation matches the change artifacts (specs, tasks, design).
+
+**Input**: Optionally specify a change name after \`/ps:verify\` (e.g., \`/ps:verify 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 changes that have implementation tasks (tasks artifact exists).
+   Include the schema used for each change if available.
+   Mark changes with incomplete tasks as "(In Progress)".
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **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\`, \`artifactPaths\`, and \`actionContext\`: path and scope context
+   - Which artifacts exist for this change
+
+   If status reports \`actionContext.mode: "workspace-planning"\`, explain that full workspace implementation verification is not supported in this slice and STOP. Do not infer repo-local implementation ownership or edit linked repos.
+
+3. **Get planning context and load artifacts**
+
+   \`\`\`bash
+   pscode instructions apply --change "<name>" --json
+   \`\`\`
+
+   This returns the change directory and \`contextFiles\` (artifact ID -> array of concrete file paths). Read all available artifacts from \`contextFiles\`.
+
+4. **Initialize verification report structure**
+
+   Create a report structure with three dimensions:
+   - **Completeness**: Track tasks and spec coverage
+   - **Correctness**: Track requirement implementation and scenario coverage
+   - **Coherence**: Track design adherence and pattern consistency
+
+   Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
+
+5. **Verify Completeness**
+
+   **Task Completion**:
+   - If \`contextFiles.tasks\` exists, read every file path in it
+   - Parse checkboxes: \`- [ ]\` (incomplete) vs \`- [x]\` (complete)
+   - Count complete vs total tasks
+   - If incomplete tasks exist:
+     - Add CRITICAL issue for each incomplete task
+     - Recommendation: "Complete task: <description>" or "Mark as done if already implemented"
+
+   **Spec Coverage**:
+   - If delta specs exist in \`contextFiles.specs\`:
+     - Extract all requirements (marked with "### Requirement:")
+     - For each requirement:
+       - Search codebase for keywords related to the requirement
+       - Assess if implementation likely exists
+     - If requirements appear unimplemented:
+       - Add CRITICAL issue: "Requirement not found: <requirement name>"
+       - Recommendation: "Implement requirement X: <description>"
+
+6. **Verify Correctness**
+
+   **Requirement Implementation Mapping**:
+   - For each requirement from delta specs:
+     - Search codebase for implementation evidence
+     - If found, note file paths and line ranges
+     - Assess if implementation matches requirement intent
+     - If divergence detected:
+       - Add WARNING: "Implementation may diverge from spec: <details>"
+       - Recommendation: "Review <file>:<lines> against requirement X"
+
+   **Scenario Coverage**:
+   - For each scenario in delta specs (marked with "#### Scenario:"):
+     - Check if conditions are handled in code
+     - Check if tests exist covering the scenario
+     - If scenario appears uncovered:
+       - Add WARNING: "Scenario not covered: <scenario name>"
+       - Recommendation: "Add test or implementation for scenario: <description>"
+
+7. **Verify Coherence**
+
+   **Design Adherence**:
+   - If \`contextFiles.design\` exists:
+     - Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
+     - Verify implementation follows those decisions
+     - If contradiction detected:
+       - Add WARNING: "Design decision not followed: <decision>"
+       - Recommendation: "Update implementation or revise design.md to match reality"
+   - If no design.md: Skip design adherence check, note "No design.md to verify against"
+
+   **Code Pattern Consistency**:
+   - Review new code for consistency with project patterns
+   - Check file naming, directory structure, coding style
+   - If significant deviations found:
+     - Add SUGGESTION: "Code pattern deviation: <details>"
+     - Recommendation: "Consider following project pattern: <example>"
+
+8. **Generate Verification Report**
+
+   **Summary Scorecard**:
+   \`\`\`
+   ## Verification Report: <change-name>
+
+   ### Summary
+   | Dimension    | Status           |
+   |--------------|------------------|
+   | Completeness | X/Y tasks, N reqs|
+   | Correctness  | M/N reqs covered |
+   | Coherence    | Followed/Issues  |
+   \`\`\`
+
+   **Issues by Priority**:
+
+   1. **CRITICAL** (Must fix before archive):
+      - Incomplete tasks
+      - Missing requirement implementations
+      - Each with specific, actionable recommendation
+
+   2. **WARNING** (Should fix):
+      - Spec/design divergences
+      - Missing scenario coverage
+      - Each with specific recommendation
+
+   3. **SUGGESTION** (Nice to fix):
+      - Pattern inconsistencies
+      - Minor improvements
+      - Each with specific recommendation
+
+   **Final Assessment**:
+   - If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
+   - If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
+   - If all clear: "All checks passed. Ready for archive."
+
+**Verification Heuristics**
+
+- **Completeness**: Focus on objective checklist items (checkboxes, requirements list)
+- **Correctness**: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
+- **Coherence**: Look for glaring inconsistencies, don't nitpick style
+- **False Positives**: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
+- **Actionability**: Every issue must have a specific recommendation with file/line references where applicable
+
+**Graceful Degradation**
+
+- If only tasks.md exists: verify task completion only, skip spec/design checks
+- If tasks + specs exist: verify completeness and correctness, skip design
+- If full artifacts: verify all three dimensions
+- Always note which checks were skipped and why
+
+**Output Format**
+
+Use clear markdown with:
+- Table for summary scorecard
+- Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
+- Code references in format: \`file.ts:123\`
+- Specific, actionable recommendations
+- No vague suggestions like "consider reviewing"`
+    };
+}
+//# sourceMappingURL=verify-change.js.map

package/dist/core/trello-config.d.ts

@@ -0,0 +1,90 @@
+/**
+ * Trello Configuration
+ *
+ * Types and utilities for reading the optional `pscode/trello.yaml`
+ * integration file. This file is created by /ps:trello-setup and
+ * consumed at runtime by all Trello-aware skills and commands.
+ */
+export interface TrelloListEntry {
+    id: string;
+    name: string;
+}
+/**
+ * Semantic stage keys that map to Trello lists.
+ * Not all stages need to be configured — unused stages are omitted.
+ */
+export interface TrelloListMap {
+    /** Ideias, rascunhos e tarefas pré-refinadas — "Backlog" */
+    backlog?: TrelloListEntry;
+    /** Em discussão / especificação — "Em Refinamento" */
+    refining?: TrelloListEntry;
+    /** Aprovadas, prontas para dev — "Ready to Dev" */
+    ready?: TrelloListEntry;
+    /** Em desenvolvimento / implementação — "Em Desenvolvimento" */
+    developing?: TrelloListEntry;
+    /** Em validação / QA — "Em Teste" */
+    testing?: TrelloListEntry;
+    /** Aprovadas para ir a produção — "Ready to Deploy" */
+    deploy?: TrelloListEntry;
+    /** Entregues / arquivadas — "Concluído" */
+    done?: TrelloListEntry;
+    /** Descartadas — "Cancelado" */
+    cancelled?: TrelloListEntry;
+}
+/**
+ * Chaves de label predefinidas no Pscode.
+ */
+export type TrelloLabelKey = 'bug' | 'implementacao' | 'melhoria' | 'debito-tecnico';
+export interface TrelloLabelEntry {
+    /** ID da etiqueta no Trello (obtido após criação via MCP) */
+    id: string;
+    /** Nome exibido na etiqueta */
+    name: string;
+    /** Cor da etiqueta no Trello (red, blue, green, orange, …) */
+    color: string;
+}
+/** Configuração de labels — presente quando o usuário optou por usá-las. */
+export interface TrelloLabelsConfig {
+    /** Se false, o agente não aplica labels nos cards. */
+    enabled: boolean;
+    /** Map de chave semântica → entrada de label no Trello. */
+    items?: Partial<Record<TrelloLabelKey, TrelloLabelEntry>>;
+}
+/** Definição estática de cada label padrão do Pscode. */
+export interface LabelDefinition {
+    key: TrelloLabelKey;
+    name: string;
+    color: string;
+    emoji: string;
+    description: string;
+}
+/**
+ * Definições canônicas das labels do Pscode.
+ * Usadas tanto na CLI (trello-init-prompt) quanto nos templates de skill.
+ */
+export declare const DEFAULT_LABEL_DEFINITIONS: LabelDefinition[];
+export interface TrelloConfig {
+    /** Trello board ID */
+    boardId: string;
+    /** Board display name (informational only) */
+    boardName?: string;
+    /** List ID map keyed by semantic stage */
+    lists: TrelloListMap;
+    /** Labels/etiquetas configuradas no board — presente quando o usuário optou por usá-las */
+    labels?: TrelloLabelsConfig;
+}
+export declare const TRELLO_CONFIG_FILENAME = "trello.yaml";
+/**
+ * Returns the expected path for `pscode/trello.yaml` relative to a project root.
+ */
+export declare function getTrelloConfigPath(projectPath: string): string;
+/**
+ * Reads `pscode/trello.yaml` from the given project root.
+ * Returns `null` if the file does not exist or is unparseable.
+ */
+export declare function readTrelloConfig(projectPath: string): TrelloConfig | null;
+/**
+ * Writes a `TrelloConfig` to `pscode/trello.yaml`.
+ */
+export declare function writeTrelloConfig(projectPath: string, config: TrelloConfig): void;
+//# sourceMappingURL=trello-config.d.ts.map

package/dist/core/trello-config.js

@@ -0,0 +1,86 @@
+/**
+ * Trello Configuration
+ *
+ * Types and utilities for reading the optional `pscode/trello.yaml`
+ * integration file. This file is created by /ps:trello-setup and
+ * consumed at runtime by all Trello-aware skills and commands.
+ */
+import * as fs from 'fs';
+import * as path from 'path';
+import { parse as parseYaml, stringify as stringifyYaml } from 'yaml';
+/**
+ * Definições canônicas das labels do Pscode.
+ * Usadas tanto na CLI (trello-init-prompt) quanto nos templates de skill.
+ */
+export const DEFAULT_LABEL_DEFINITIONS = [
+    {
+        key: 'bug',
+        name: 'BUG',
+        color: 'red',
+        emoji: '🐛',
+        description: 'Erro ou comportamento incorreto que precisa ser corrigido',
+    },
+    {
+        key: 'implementacao',
+        name: 'IMPLEMENTAÇÃO',
+        color: 'blue',
+        emoji: '⚙️',
+        description: 'Nova funcionalidade desenvolvida do zero',
+    },
+    {
+        key: 'melhoria',
+        name: 'MELHORIA',
+        color: 'green',
+        emoji: '✨',
+        description: 'Aperfeiçoamento ou otimização de algo existente',
+    },
+    {
+        key: 'debito-tecnico',
+        name: 'DÉBITO TÉCNICO',
+        color: 'orange',
+        emoji: '💳',
+        description: 'Refatoração, limpeza de código ou resolução de dívida técnica',
+    },
+];
+// ─────────────────────────────────────────────────────────────────────────────
+// File path resolution
+// ─────────────────────────────────────────────────────────────────────────────
+export const TRELLO_CONFIG_FILENAME = 'trello.yaml';
+/**
+ * Returns the expected path for `pscode/trello.yaml` relative to a project root.
+ */
+export function getTrelloConfigPath(projectPath) {
+    return path.join(projectPath, 'pscode', TRELLO_CONFIG_FILENAME);
+}
+// ─────────────────────────────────────────────────────────────────────────────
+// Read / Write
+// ─────────────────────────────────────────────────────────────────────────────
+/**
+ * Reads `pscode/trello.yaml` from the given project root.
+ * Returns `null` if the file does not exist or is unparseable.
+ */
+export function readTrelloConfig(projectPath) {
+    const configPath = getTrelloConfigPath(projectPath);
+    try {
+        if (!fs.existsSync(configPath))
+            return null;
+        const raw = fs.readFileSync(configPath, 'utf-8');
+        const parsed = parseYaml(raw);
+        if (!parsed?.boardId || !parsed?.lists)
+            return null;
+        return parsed;
+    }
+    catch {
+        return null;
+    }
+}
+/**
+ * Writes a `TrelloConfig` to `pscode/trello.yaml`.
+ */
+export function writeTrelloConfig(projectPath, config) {
+    const configPath = getTrelloConfigPath(projectPath);
+    const yaml = stringifyYaml(config, { lineWidth: 0 });
+    fs.mkdirSync(path.dirname(configPath), { recursive: true });
+    fs.writeFileSync(configPath, yaml, 'utf-8');
+}
+//# sourceMappingURL=trello-config.js.map

package/dist/core/trello-init-prompt.d.ts

@@ -0,0 +1,61 @@
+/**
+ * Trello Init Prompt
+ *
+ * Handles the interactive Trello setup questions during `pscode init`.
+ * Saves a partial `pscode/trello.yaml` with `configured: false` so that
+ * `/ps:trello-setup` (in Claude Code) can pick up where the CLI left off
+ * and only needs to perform the MCP-dependent steps (list lookup/creation).
+ */
+import { type TrelloLabelKey } from './trello-config.js';
+export interface StageDefinition {
+    key: string;
+    defaultName: string;
+    emoji: string;
+    description: string;
+    required?: boolean;
+}
+export declare const ALL_STAGES: StageDefinition[];
+export interface PendingLabelsConfig {
+    /** Se o usuário optou por usar labels */
+    enabled: boolean;
+    /** Chaves das labels selecionadas (subconjunto de DEFAULT_LABEL_DEFINITIONS) */
+    selected?: TrelloLabelKey[];
+}
+export interface TrelloPendingConfig {
+    /** Always false when saved by CLI init — completed by /ps:trello-setup */
+    configured: false;
+    /** Whether the user indicated they already have a Trello board */
+    hasExistingBoard: boolean;
+    /** Board ID provided by the user (only if hasExistingBoard = true) */
+    boardId?: string;
+    /** Selected stage keys in order */
+    stages: string[];
+    /** Custom names for each selected stage (overrides defaults) */
+    stageNames: Record<string, string>;
+    /** Labels/etiquetas — presente quando o usuário optou por configurar labels */
+    labels?: PendingLabelsConfig;
+}
+export interface TrelloCompleteConfig {
+    configured: true;
+    boardId: string;
+    boardName?: string;
+    lists: Record<string, {
+        id: string;
+        name: string;
+    }>;
+    labels?: {
+        enabled: boolean;
+        items?: Record<string, {
+            id: string;
+            name: string;
+            color: string;
+        }>;
+    };
+}
+export type TrelloYamlConfig = TrelloPendingConfig | TrelloCompleteConfig;
+/**
+ * Runs the interactive Trello setup questions during `pscode init`.
+ * Returns whether the user chose to set up Trello.
+ */
+export declare function runTrelloInitPrompt(pscodePath: string): Promise<boolean>;
+//# sourceMappingURL=trello-init-prompt.d.ts.map