@urielsh/prodify 0.1.0

package/assets/presets/default/canonical/contracts-src/validate.contract.md

@@ -0,0 +1,64 @@
+---
+schema_version: 1
+contract_version: 1.0.0
+stage: validate
+task_id: 06-validate
+required_artifacts:
+  - path: .prodify/artifacts/06-validate.md
+    format: markdown
+    required_sections:
+      - Policy Checks
+      - Regressions
+      - Success Criteria
+      - Validation Results
+  - path: .prodify/state.json
+    format: json
+    required_json_keys:
+      - preset_name
+      - preset_version
+      - runtime
+      - schema_version
+allowed_write_roots:
+  - .prodify/artifacts/
+  - .prodify/metrics/
+forbidden_writes:
+  - src/
+policy_rules:
+  - Validation must follow every refactor step.
+  - Critical regressions block forward progress.
+success_criteria:
+  - Validation records whether regressions were found.
+  - The result is strong enough to gate the next runtime transition.
+skill_routing:
+  default_skills:
+    - test-hardening
+    - validation-method
+  allowed_skills:
+    - react-frontend
+    - security-hardening
+    - test-hardening
+    - typescript-backend
+    - validation-method
+  conditional_skills:
+    - skill: react-frontend
+      when:
+        all:
+          - fact: framework
+            includes: react
+      reason: repo framework includes React
+    - skill: security-hardening
+      when:
+        all:
+          - fact: risk_signal
+            includes: external-dependencies
+      reason: repo carries external dependency risk
+    - skill: typescript-backend
+      when:
+        all:
+          - fact: language
+            includes: typescript
+      reason: repo language includes TypeScript
+---
+# Validate Contract
+
+Use this contract to record validation evidence, regression status, and final readiness for the next state transition.

package/assets/presets/default/canonical/metrics/README.md

@@ -0,0 +1,4 @@
+# Local Metrics
+
+Prodify writes local baseline, final, and delta score artifacts here.
+Normalized score outputs and raw tool outputs stay separate.

package/assets/presets/default/canonical/planning.md

@@ -0,0 +1,13 @@
+# Planning
+
+## Current Milestone
+
+Describe the current milestone here.
+
+## Backlog
+
+- Add upcoming work items here.
+
+## Open Decisions
+
+- Record decisions that still need resolution.

package/assets/presets/default/canonical/project.md

@@ -0,0 +1,15 @@
+# Project
+
+## Summary
+
+Describe the repository purpose here.
+
+## Goals
+
+- Capture project goals.
+- Record constraints and conventions.
+
+## Agent Bootstrap
+
+- The user starts by telling the agent to read `.prodify/AGENTS.md`.
+- The main Prodify flow should stay inside `.prodify/`.

package/assets/presets/default/canonical/rules/README.md

@@ -0,0 +1,3 @@
+# Prodify Rules
+
+This directory is reserved for rule documents that refine the default workflow for the current repository.

package/assets/presets/default/canonical/rules/example-rule.md

@@ -0,0 +1,4 @@
+# Example Rule
+
+- Keep generated output deterministic.
+- Prefer canonical edits over generated-file edits.

package/assets/presets/default/canonical/runtime-commands.md

@@ -0,0 +1,57 @@
+# Runtime Commands
+
+Run these commands inside your coding agent after `prodify init`.
+If this machine has not been prepared for that agent yet, run `prodify setup-agent <agent>` outside the repo first.
+
+## Manual Bootstrap
+
+- First tell the agent: `Read .prodify/AGENTS.md and bootstrap Prodify for this repository.`
+- Keep the run anchored to `.prodify/AGENTS.md`, `.prodify/project.md`, `.prodify/planning.md`, `.prodify/contracts-src/`, `.prodify/contracts/`, `.prodify/skills/`, `.prodify/artifacts/`, `.prodify/metrics/`, `.prodify/tasks/`, and `.prodify/state.json`.
+
+## Commands
+
+- `$prodify-init`
+  - inspect `.prodify/`
+  - detect or resolve the active agent/runtime mode
+  - initialize `.prodify/state.json`
+  - prepare the bootstrapped state and the `understand` contract without locking the repo to one agent
+
+- `$prodify-execute`
+  - run one workflow stage
+  - write stage artifacts under `.prodify/artifacts/`
+  - validate the stage against the compiled contract JSON
+  - update runtime state after the validation result
+  - pause for validation checkpoints between stages in interactive mode
+
+- `$prodify-execute --auto`
+  - continue across stages without pausing
+  - stop only on hard failure, policy block, required approval threshold, or invalid state
+
+- `$prodify-resume`
+  - continue from `.prodify/state.json`
+  - preserve validation checkpoints
+  - fail clearly if the state is corrupt or non-resumable
+
+## Supported Runtime Profiles
+
+- Codex
+- Claude
+- Copilot
+- OpenCode
+
+## Stage Order
+
+- `understand`
+- `diagnose`
+- `architecture`
+- `plan`
+- `refactor`
+- `validate`
+
+## Contract Rules
+
+- Source contracts live under `.prodify/contracts-src/*.contract.md`.
+- Runtime execution reads only `.prodify/contracts/*.contract.json`.
+- Skill definitions live under `.prodify/skills/*.json`.
+- Stage skill routing can activate bounded skills per stage, but contracts and validators remain authoritative.
+- Stage completion is gated by compiled-contract validation, not by agent assertion alone.

package/assets/presets/default/canonical/skills/README.md

@@ -0,0 +1,8 @@
+# Skills
+
+This directory contains the product-owned skill registry for deterministic stage execution.
+
+- `registry.json` is the manifest and source of truth for discoverable skills.
+- Each `*.skill.json` file defines one bounded skill.
+- Contracts may reference skills only through explicit `skill_routing`.
+- Skills can improve execution quality, but they never override compiled contracts or validation.

package/assets/presets/default/canonical/skills/domain/react-frontend.skill.json

@@ -0,0 +1,34 @@
+{
+  "schema_version": "1",
+  "id": "react-frontend",
+  "name": "React Frontend",
+  "version": "1.0.0",
+  "category": "domain",
+  "description": "Provides React-specific implementation and review guidance when a React surface is detected.",
+  "intended_use": [
+    "Use in understand, architecture, refactor, and validate when the repo framework includes React."
+  ],
+  "stage_compatibility": [
+    "architecture",
+    "refactor",
+    "understand",
+    "validate"
+  ],
+  "activation_conditions": [
+    {
+      "all": [
+        {
+          "fact": "framework",
+          "includes": "react"
+        }
+      ]
+    }
+  ],
+  "execution_guidance": [
+    "Preserve component boundaries and data-flow clarity.",
+    "Keep framework-specific advice subordinate to stage contracts."
+  ],
+  "caution_guidance": [
+    "Do not assume a frontend repo unless React evidence is present."
+  ]
+}

package/assets/presets/default/canonical/skills/domain/typescript-backend.skill.json

@@ -0,0 +1,34 @@
+{
+  "schema_version": "1",
+  "id": "typescript-backend",
+  "name": "TypeScript Backend",
+  "version": "1.0.0",
+  "category": "domain",
+  "description": "Applies TypeScript service and CLI implementation guidance when the repository is TypeScript-based.",
+  "intended_use": [
+    "Use in architecture, refactor, and validate when the repo language includes TypeScript."
+  ],
+  "stage_compatibility": [
+    "architecture",
+    "refactor",
+    "understand",
+    "validate"
+  ],
+  "activation_conditions": [
+    {
+      "all": [
+        {
+          "fact": "language",
+          "includes": "typescript"
+        }
+      ]
+    }
+  ],
+  "execution_guidance": [
+    "Prefer type-safe interfaces and explicit runtime-state normalization.",
+    "Keep generated JavaScript output aligned with TypeScript sources."
+  ],
+  "caution_guidance": [
+    "Do not rely on implicit any-style assumptions when shaping refactors."
+  ]
+}

package/assets/presets/default/canonical/skills/quality-policy/maintainability-review.skill.json

@@ -0,0 +1,25 @@
+{
+  "schema_version": "1",
+  "id": "maintainability-review",
+  "name": "Maintainability Review",
+  "version": "1.0.0",
+  "category": "quality-policy",
+  "description": "Highlights readability, ownership, and long-term support risks without redefining success criteria.",
+  "intended_use": [
+    "Use in diagnose, architecture, and plan when maintainability concerns are relevant."
+  ],
+  "stage_compatibility": [
+    "architecture",
+    "diagnose",
+    "plan",
+    "understand"
+  ],
+  "activation_conditions": [],
+  "execution_guidance": [
+    "Call out mixed concerns and unclear ownership paths.",
+    "Prefer small, explainable structure improvements."
+  ],
+  "caution_guidance": [
+    "Do not replace contract validation with style preference."
+  ]
+}

package/assets/presets/default/canonical/skills/quality-policy/security-hardening.skill.json

@@ -0,0 +1,32 @@
+{
+  "schema_version": "1",
+  "id": "security-hardening",
+  "name": "Security Hardening",
+  "version": "1.0.0",
+  "category": "quality-policy",
+  "description": "Applies explicit scrutiny when the repository has exposed surfaces or dependency risk signals.",
+  "intended_use": [
+    "Use in diagnose and validate when risk signals suggest stronger security review."
+  ],
+  "stage_compatibility": [
+    "diagnose",
+    "validate"
+  ],
+  "activation_conditions": [
+    {
+      "all": [
+        {
+          "fact": "risk_signal",
+          "includes": "external-dependencies"
+        }
+      ]
+    }
+  ],
+  "execution_guidance": [
+    "Check exposed command or network surfaces before declaring validation success.",
+    "Treat dependency-driven risk as additive evidence, not a blocker by itself."
+  ],
+  "caution_guidance": [
+    "Do not infer a security defect without repository evidence."
+  ]
+}

package/assets/presets/default/canonical/skills/quality-policy/test-hardening.skill.json

@@ -0,0 +1,23 @@
+{
+  "schema_version": "1",
+  "id": "test-hardening",
+  "name": "Test Hardening",
+  "version": "1.0.0",
+  "category": "quality-policy",
+  "description": "Improves confidence through regression-focused test additions or validation checks.",
+  "intended_use": [
+    "Use in refactor and validate when executable checks should be strengthened."
+  ],
+  "stage_compatibility": [
+    "refactor",
+    "validate"
+  ],
+  "activation_conditions": [],
+  "execution_guidance": [
+    "Add or strengthen tests around the selected behavior change boundary.",
+    "Prefer deterministic assertions over snapshot-like broad checks."
+  ],
+  "caution_guidance": [
+    "Do not add unrelated test churn outside the selected step."
+  ]
+}

package/assets/presets/default/canonical/skills/registry.json

@@ -0,0 +1,16 @@
+{
+  "schema_version": "1",
+  "skills": [
+    "domain/react-frontend.skill.json",
+    "domain/typescript-backend.skill.json",
+    "quality-policy/maintainability-review.skill.json",
+    "quality-policy/security-hardening.skill.json",
+    "quality-policy/test-hardening.skill.json",
+    "stage-method/architecture-method.skill.json",
+    "stage-method/codebase-scanning.skill.json",
+    "stage-method/diagnosis-method.skill.json",
+    "stage-method/planning-method.skill.json",
+    "stage-method/refactoring-method.skill.json",
+    "stage-method/validation-method.skill.json"
+  ]
+}

package/assets/presets/default/canonical/skills/stage-method/architecture-method.skill.json

@@ -0,0 +1,22 @@
+{
+  "schema_version": "1",
+  "id": "architecture-method",
+  "name": "Architecture Method",
+  "version": "1.0.0",
+  "category": "stage-method",
+  "description": "Focuses architecture work on boundaries, dependency direction, and modular responsibility splits.",
+  "intended_use": [
+    "Use during architecture to propose structural changes that preserve the contract model."
+  ],
+  "stage_compatibility": [
+    "architecture"
+  ],
+  "activation_conditions": [],
+  "execution_guidance": [
+    "Describe boundaries before proposing new modules or layers.",
+    "Flag mixed concerns and outward domain dependencies explicitly."
+  ],
+  "caution_guidance": [
+    "Do not treat architecture guidance as permission to rewrite unrelated code."
+  ]
+}

package/assets/presets/default/canonical/skills/stage-method/codebase-scanning.skill.json

@@ -0,0 +1,22 @@
+{
+  "schema_version": "1",
+  "id": "codebase-scanning",
+  "name": "Codebase Scanning",
+  "version": "1.0.0",
+  "category": "stage-method",
+  "description": "Guides the understand stage toward deterministic inventory, dependency, and ownership mapping.",
+  "intended_use": [
+    "Use during understand to scan the repository surface before drawing conclusions."
+  ],
+  "stage_compatibility": [
+    "understand"
+  ],
+  "activation_conditions": [],
+  "execution_guidance": [
+    "Inventory verified files and directories before summarizing the repository.",
+    "Prefer direct evidence over inferred structure."
+  ],
+  "caution_guidance": [
+    "Do not speculate about missing modules or undocumented ownership."
+  ]
+}

package/assets/presets/default/canonical/skills/stage-method/diagnosis-method.skill.json

@@ -0,0 +1,22 @@
+{
+  "schema_version": "1",
+  "id": "diagnosis-method",
+  "name": "Diagnosis Method",
+  "version": "1.0.0",
+  "category": "stage-method",
+  "description": "Keeps diagnosis anchored to observed evidence, root causes, and production-readiness risks.",
+  "intended_use": [
+    "Use during diagnose to separate symptoms, causes, and unsupported claims."
+  ],
+  "stage_compatibility": [
+    "diagnose"
+  ],
+  "activation_conditions": [],
+  "execution_guidance": [
+    "Tie every issue to observable evidence.",
+    "Separate root causes from downstream symptoms."
+  ],
+  "caution_guidance": [
+    "Do not prescribe implementation changes in the diagnosis stage."
+  ]
+}

package/assets/presets/default/canonical/skills/stage-method/planning-method.skill.json

@@ -0,0 +1,22 @@
+{
+  "schema_version": "1",
+  "id": "planning-method",
+  "name": "Planning Method",
+  "version": "1.0.0",
+  "category": "stage-method",
+  "description": "Shapes implementation plans into bounded, testable, behavior-preserving steps.",
+  "intended_use": [
+    "Use during plan to convert diagnosis and architecture outputs into ordered steps."
+  ],
+  "stage_compatibility": [
+    "plan"
+  ],
+  "activation_conditions": [],
+  "execution_guidance": [
+    "Keep steps small, testable, and directly linked to diagnosed issues.",
+    "Call out guardrails when behavior must remain stable."
+  ],
+  "caution_guidance": [
+    "Do not introduce implementation detail that belongs in refactor."
+  ]
+}

package/assets/presets/default/canonical/skills/stage-method/refactoring-method.skill.json

@@ -0,0 +1,22 @@
+{
+  "schema_version": "1",
+  "id": "refactoring-method",
+  "name": "Refactoring Method",
+  "version": "1.0.0",
+  "category": "stage-method",
+  "description": "Keeps refactor work bounded to a single selected step with minimal diff discipline.",
+  "intended_use": [
+    "Use during refactor when implementing one approved plan step."
+  ],
+  "stage_compatibility": [
+    "refactor"
+  ],
+  "activation_conditions": [],
+  "execution_guidance": [
+    "Implement one planned step at a time.",
+    "Preserve behavior unless the plan explicitly authorizes a change."
+  ],
+  "caution_guidance": [
+    "Do not expand the edit set beyond the selected step."
+  ]
+}

package/assets/presets/default/canonical/skills/stage-method/validation-method.skill.json

@@ -0,0 +1,22 @@
+{
+  "schema_version": "1",
+  "id": "validation-method",
+  "name": "Validation Method",
+  "version": "1.0.0",
+  "category": "stage-method",
+  "description": "Ensures validation checks regressions, contract conformance, and structural improvements explicitly.",
+  "intended_use": [
+    "Use during validate to assess pass or fail after refactor work."
+  ],
+  "stage_compatibility": [
+    "validate"
+  ],
+  "activation_conditions": [],
+  "execution_guidance": [
+    "Check contract conformance before interpreting broader quality signals.",
+    "Record regressions and architecture violations explicitly."
+  ],
+  "caution_guidance": [
+    "Do not treat validation as optional after refactor."
+  ]
+}

package/assets/presets/default/canonical/state.json

@@ -0,0 +1,30 @@
+{
+  "schema_version": "2",
+  "preset_name": "default",
+  "preset_version": "4.0.0",
+  "runtime": {
+    "status": "not_bootstrapped",
+    "current_state": "not_bootstrapped",
+    "mode": null,
+    "current_stage": null,
+    "current_task_id": null,
+    "pending_stage": null,
+    "completed_stages": [],
+    "awaiting_user_validation": false,
+    "last_validation_result": "unknown",
+    "last_validation": null,
+    "last_validated_contract_versions": {},
+    "resumable": false,
+    "blocked_reason": null,
+    "failure_metadata": null,
+    "bootstrap": {
+      "bootstrapped": false
+    },
+    "next_action": "$prodify-init",
+    "timestamps": {
+      "bootstrapped_at": null,
+      "last_transition_at": null,
+      "completed_at": null
+    }
+  }
+}

package/assets/presets/default/canonical/tasks/README.md

@@ -0,0 +1,3 @@
+# Prodify Tasks
+
+This directory is reserved for task-scoped runtime artifacts and deterministic task definitions when a repository extends the default flow.

package/assets/presets/default/canonical/tasks/example-task.md

@@ -0,0 +1,13 @@
+# Example Task
+
+## Goal
+
+Describe the task goal.
+
+## Inputs
+
+- List required inputs.
+
+## Output
+
+- Describe the expected output.

package/assets/presets/default/canonical/templates/README.md

@@ -0,0 +1,3 @@
+# Prodify Templates
+
+This directory is reserved for repository-local templates that the runtime may need while executing the Prodify workflow.

package/assets/presets/default/canonical/templates/example.template.md

@@ -0,0 +1,5 @@
+# Example Template
+
+## Section
+
+Fill this section explicitly.

package/assets/presets/default/preset.json

@@ -0,0 +1,5 @@
+{
+  "name": "default",
+  "version": "4.0.0",
+  "schemaVersion": "4"
+}

package/dist/cli.js

@@ -0,0 +1,53 @@
+import { runDoctorCommand } from './commands/doctor.js';
+import { runInitCommand } from './commands/init.js';
+import { runSetupAgentCommand } from './commands/setup-agent.js';
+import { runStatusCommand } from './commands/status.js';
+import { runUpdateCommand } from './commands/update.js';
+import { ProdifyError, toErrorMessage } from './core/errors.js';
+export const COMMANDS = {
+    init: runInitCommand,
+    'setup-agent': runSetupAgentCommand,
+    status: runStatusCommand,
+    doctor: runDoctorCommand,
+    update: runUpdateCommand
+};
+export const PUBLIC_COMMANDS = ['init', 'setup-agent', 'status', 'doctor', 'update'];
+export function renderHelp() {
+    return [
+        'Prodify CLI',
+        '',
+        'Usage:',
+        '  prodify setup-agent <codex|claude|copilot|opencode>',
+        '  prodify init',
+        '  prodify status',
+        '  prodify doctor',
+        '  prodify update',
+        '',
+        'Global agent setup is separate from per-repository init.',
+        'The primary flow is .prodify-first and contract-driven.'
+    ].join('\n');
+}
+export async function runCli(argv, context = {}) {
+    const stdout = context.stdout ?? process.stdout;
+    const stderr = context.stderr ?? process.stderr;
+    const cwd = context.cwd ?? process.cwd();
+    if (argv.length === 0 || argv.includes('--help') || argv.includes('-h')) {
+        stdout.write(`${renderHelp()}\n`);
+        return 0;
+    }
+    const [commandName, ...rest] = argv;
+    const command = COMMANDS[commandName];
+    if (!command) {
+        stderr.write(`Unknown command: ${commandName}\n`);
+        stderr.write(`${renderHelp()}\n`);
+        return 1;
+    }
+    try {
+        return await command(rest, { cwd, stdout, stderr });
+    }
+    catch (error) {
+        const message = toErrorMessage(error);
+        stderr.write(`${message}\n`);
+        return error instanceof ProdifyError ? error.exitCode : 1;
+    }
+}

package/dist/commands/doctor.js

@@ -0,0 +1,16 @@
+import { resolveRepoRoot } from '../core/repo-root.js';
+import { runDoctor } from '../core/doctor.js';
+export async function runDoctorCommand(args, context) {
+    void args;
+    const repoRoot = await resolveRepoRoot({
+        cwd: context.cwd,
+        allowBootstrap: true
+    });
+    const result = await runDoctor(repoRoot);
+    context.stdout.write('Prodify Doctor\n');
+    for (const check of result.checks) {
+        const status = check.skipped ? 'SKIP' : check.ok ? 'PASS' : 'FAIL';
+        context.stdout.write(`${check.label}: ${status}${check.details ? ` - ${check.details}` : ''}\n`);
+    }
+    return result.ok ? 0 : 1;
+}

package/dist/commands/init.js

@@ -0,0 +1,30 @@
+import { writeFileEnsuringDir } from '../core/fs.js';
+import { resolveRepoRoot } from '../core/repo-root.js';
+import { resolveRepoPath } from '../core/paths.js';
+import { pathExists } from '../core/fs.js';
+import { ProdifyError } from '../core/errors.js';
+import { loadDefaultPreset } from '../presets/loader.js';
+import { synchronizeRuntimeContracts } from '../contracts/compiler.js';
+export async function runInitCommand(args, context) {
+    void args;
+    const repoRoot = await resolveRepoRoot({
+        cwd: context.cwd,
+        allowBootstrap: true
+    });
+    const prodifyDir = resolveRepoPath(repoRoot, '.prodify');
+    if (await pathExists(prodifyDir)) {
+        throw new ProdifyError('.prodify/ already exists. init stops rather than merging existing canonical files.', {
+            code: 'PRODIFY_ALREADY_EXISTS'
+        });
+    }
+    const preset = await loadDefaultPreset();
+    for (const entry of preset.entries) {
+        await writeFileEnsuringDir(resolveRepoPath(repoRoot, entry.relativePath), entry.content);
+    }
+    await synchronizeRuntimeContracts(repoRoot);
+    context.stdout.write(`Initialized Prodify in ${repoRoot}\n`);
+    context.stdout.write('Global agent setup is separate: run `prodify setup-agent <agent>` once per machine before using `$prodify-*` commands inside that agent\n');
+    context.stdout.write('Manual bootstrap starts by telling your agent to read .prodify/AGENTS.md\n');
+    context.stdout.write('Compiled runtime contracts were generated under .prodify/contracts/\n');
+    return 0;
+}