@urielsh/prodify 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "[]"
+replaced with your own identifying information. (Don't include
+the brackets!) The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -0,0 +1,118 @@
+# Prodify
+
+Prodify turns AI- or vibe-coded repositories into production-grade code through a deterministic, agent-native workflow.
+
+## Product Purpose
+
+Fast AI-generated code drifts into inconsistent structure, weak validation, and unclear ownership. Prodify gives that repo a repeatable upgrade path instead of relying on ad hoc prompting.
+
+## Architecture
+
+Prodify has two layers:
+
+- external CLI for repository setup and health
+- inside-agent runtime commands for actually running the contract-driven transformation flow
+
+External CLI:
+
+- `prodify init`
+- `prodify status`
+- `prodify doctor`
+- `prodify update`
+
+Inside the agent:
+
+- read `.prodify/AGENTS.md`
+- `$prodify-init`
+- `$prodify-execute`
+- `$prodify-execute --auto`
+- `$prodify-resume`
+
+## Repo Model
+
+- `.prodify/` is the only required product-owned footprint.
+- No root-level agent files are required in the default flow.
+- If this repository contains a root `AGENTS.md`, treat it as repository-local contributor guidance for developing Prodify itself, not as a generated or required product runtime file.
+- All durable workflow state lives in `.prodify/`.
+- Humans edit stage contracts under `.prodify/contracts-src/`.
+- Runtime execution reads only compiled contracts under `.prodify/contracts/`.
+- Product-owned skill definitions live under `.prodify/skills/`.
+- Stage outputs live under `.prodify/artifacts/`.
+- Local baseline/final/delta scoring lives under `.prodify/metrics/`.
+- This repository’s checked-in repo-root `.prodify/` directory is the self-hosting workspace for Prodify itself. It includes the generated runtime layout plus repo-specific design and development artifacts, so it is not a byte-for-byte snapshot of fresh `prodify init` output.
+
+## User Flow
+
+1. Set up an agent once per machine:
+
+```sh
+prodify setup-agent codex
+```
+
+2. Initialize the repository:
+
+```sh
+npm run build
+node ./dist/index.js init
+```
+
+3. Open the supported agent you want to use.
+
+- Codex
+- Claude
+- Copilot
+- OpenCode
+
+4. Tell it: `Read .prodify/AGENTS.md and bootstrap Prodify for this repository.`
+
+5. Inside that agent, run `$prodify-init`.
+
+6. Run `$prodify-execute` for stage-by-stage execution, or `$prodify-execute --auto` to continue until a hard stop.
+
+7. If the flow pauses for validation or is interrupted, continue with `$prodify-resume`.
+8. Use `prodify status`, `prodify doctor`, and `prodify update` from the CLI to inspect or refresh the `.prodify/` scaffolding, compiled contracts, and local metrics workspace.
+
+Repo initialization stays agent-agnostic. The active agent is resolved when `$prodify-init` runs inside the opened agent, not when `prodify init` creates `.prodify/`.
+
+## Contracts And Validation
+
+- Contract source files are Markdown with YAML frontmatter under `.prodify/contracts-src/`.
+- `prodify init` and `prodify update` compile those sources into deterministic runtime JSON under `.prodify/contracts/`.
+- Each stage can also declare bounded `skill_routing` metadata, while concrete skill definitions stay versioned under `.prodify/skills/`.
+- Status can report which stage skills were considered and activated from repository context, but contracts and validators remain authoritative.
+- Stage completion is gated by compiled-contract validation, not by agent assertion alone.
+- Validation checks required artifacts, write boundaries, forbidden writes, Markdown sections, JSON keys, and contract criteria.
+
+## Local Scoring
+
+- Prodify can persist local baseline, final, and delta score artifacts under `.prodify/metrics/`.
+- Raw tool outputs and normalized scores are stored separately so the score is traceable and deterministic.
+
+## Supported Agents
+
+- Codex
+- Claude
+- Copilot
+- OpenCode
+
+All supported agents use the same `.prodify/AGENTS.md` bootstrap path in the current product model.
+
+## Development
+
+Run the test suite:
+
+```sh
+npm test
+```
+
+The implementation lives primarily in:
+- `src/`
+- `assets/presets/default/`
+- `tests/`
+- `docs/`
+
+Repository-local contributor guidance for this self-hosted repo lives in root [AGENTS.md](/Users/urielsh/projects/prodify/AGENTS.md). Product runtime guidance lives in [.prodify/AGENTS.md](/Users/urielsh/projects/prodify/.prodify/AGENTS.md).
+
+## License
+
+This project is licensed under the Apache License 2.0. See [LICENSE](./LICENSE).

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

@@ -0,0 +1,54 @@
+# Prodify Agent Entry
+
+## First Message
+
+When the user opens a coding agent manually, the first instruction should be:
+
+`Read .prodify/AGENTS.md and bootstrap Prodify for this repository.`
+
+After the agent reads this file, it should continue with `$prodify-init` and keep the full workflow anchored to `.prodify/`.
+
+## Core Rules
+
+- `.prodify/` is the only source of truth.
+- Humans edit `.prodify/contracts-src/`; runtime reads only `.prodify/contracts/*.contract.json`.
+- No root-level `AGENTS.md`, `CLAUDE.md`, `.github/copilot-instructions.md`, or `.opencode/AGENTS.md` is required for the main flow.
+- Repository initialization remains agent-agnostic. The active agent is resolved when `$prodify-init` runs, not when `prodify init` creates `.prodify/`.
+- External CLI commands prepare and inspect the repo.
+- Runtime commands are executed inside the chosen coding agent.
+- Durable workflow state lives in `.prodify/state.json`.
+
+## External CLI
+
+- `prodify init`
+- `prodify setup-agent`
+- `prodify status`
+- `prodify doctor`
+- `prodify update`
+
+## Runtime Files
+
+- `.prodify/AGENTS.md`
+- `.prodify/project.md`
+- `.prodify/planning.md`
+- `.prodify/contracts-src/`
+- `.prodify/contracts/`
+- `.prodify/skills/`
+- `.prodify/artifacts/`
+- `.prodify/metrics/`
+- `.prodify/tasks/`
+- `.prodify/state.json`
+- `.prodify/runtime-commands.md`
+
+## Stage Skill System
+
+- Contracts may declare stage-bounded `skill_routing`.
+- Concrete skill definitions live under `.prodify/skills/`.
+- Skills can improve stage execution quality, but they must not override contracts, write boundaries, or validation outcomes.
+
+## Runtime Commands
+
+- `$prodify-init`
+- `$prodify-execute`
+- `$prodify-execute --auto`
+- `$prodify-resume`

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

@@ -0,0 +1,6 @@
+# Stage Artifacts
+
+Stage execution writes validated outputs into this directory.
+Each stage contract declares the canonical artifact paths and required sections.
+The active runtime stage outputs use numbered filenames such as `01-understand.md` through `06-validate.md`.
+This self-hosted repository may also keep repository-local design or historical artifacts here when they are useful for developing Prodify itself.

package/assets/presets/default/canonical/contracts-src/README.md

@@ -0,0 +1,4 @@
+# Contract Sources
+
+Edit the human-readable Markdown contracts in this directory.
+Run `prodify update` to regenerate the compiled runtime JSON under `.prodify/contracts/`.

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

@@ -0,0 +1,56 @@
+---
+schema_version: 1
+contract_version: 1.0.0
+stage: architecture
+task_id: 03-architecture
+required_artifacts:
+  - path: .prodify/artifacts/03-architecture.md
+    format: markdown
+    required_sections:
+      - Dependency Rules
+      - Policy Checks
+      - Proposed Structure
+      - Success Criteria
+      - Tradeoffs
+allowed_write_roots:
+  - .prodify/artifacts/
+forbidden_writes:
+  - src/
+  - tests/
+policy_rules:
+  - Flag mixed concerns explicitly.
+  - Keep Domain dependencies pointing inward only.
+success_criteria:
+  - The target structure is explicit.
+  - Architecture violations are listed clearly.
+skill_routing:
+  default_skills:
+    - architecture-method
+  allowed_skills:
+    - architecture-method
+    - maintainability-review
+    - react-frontend
+    - typescript-backend
+  conditional_skills:
+    - skill: maintainability-review
+      when:
+        all:
+          - fact: architecture_pattern
+            includes: contract-driven-runtime
+      reason: contract-driven runtime boundaries need maintainability review
+    - skill: react-frontend
+      when:
+        all:
+          - fact: framework
+            includes: react
+      reason: repo framework includes React
+    - skill: typescript-backend
+      when:
+        all:
+          - fact: language
+            includes: typescript
+      reason: repo language includes TypeScript
+---
+# Architecture Contract
+
+Use this contract to define the target structure, dependency rules, and major tradeoffs before planning.

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

@@ -0,0 +1,49 @@
+---
+schema_version: 1
+contract_version: 1.0.0
+stage: diagnose
+task_id: 02-diagnose
+required_artifacts:
+  - path: .prodify/artifacts/02-diagnose.md
+    format: markdown
+    required_sections:
+      - Constraints
+      - Observed Issues
+      - Policy Checks
+      - Root Causes
+      - Success Criteria
+allowed_write_roots:
+  - .prodify/artifacts/
+forbidden_writes:
+  - src/
+  - tests/
+policy_rules:
+  - Diagnose from repository evidence only.
+  - Do not propose implementation changes in the diagnosis stage.
+success_criteria:
+  - Every critical issue is tied to evidence.
+  - Root causes are separated from symptoms.
+skill_routing:
+  default_skills:
+    - diagnosis-method
+  allowed_skills:
+    - diagnosis-method
+    - maintainability-review
+    - security-hardening
+  conditional_skills:
+    - skill: maintainability-review
+      when:
+        all:
+          - fact: architecture_pattern
+            includes: layered-cli
+      reason: layered CLI ownership should be reviewed for maintainability
+    - skill: security-hardening
+      when:
+        all:
+          - fact: risk_signal
+            includes: external-dependencies
+      reason: repo carries external dependency risk
+---
+# Diagnose Contract
+
+Use this contract to record observed problems, supporting evidence, and the most likely root causes.

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

@@ -0,0 +1,42 @@
+---
+schema_version: 1
+contract_version: 1.0.0
+stage: plan
+task_id: 04-plan
+required_artifacts:
+  - path: .prodify/artifacts/04-plan.md
+    format: markdown
+    required_sections:
+      - Policy Checks
+      - Risks
+      - Step Breakdown
+      - Success Criteria
+      - Verification
+allowed_write_roots:
+  - .prodify/artifacts/
+forbidden_writes:
+  - src/
+  - tests/
+policy_rules:
+  - Keep the plan deterministic and minimal.
+  - Map every step back to a diagnosed issue or architecture rule.
+success_criteria:
+  - The plan enumerates executable steps.
+  - Verification is defined before refactoring starts.
+skill_routing:
+  default_skills:
+    - planning-method
+  allowed_skills:
+    - maintainability-review
+    - planning-method
+  conditional_skills:
+    - skill: maintainability-review
+      when:
+        all:
+          - fact: project_type
+            includes: cli
+      reason: CLI lifecycle changes should be reviewed for maintainability
+---
+# Plan Contract
+
+Use this contract to produce the smallest safe sequence of refactor steps and verification checkpoints.

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

@@ -0,0 +1,54 @@
+---
+schema_version: 1
+contract_version: 1.0.0
+stage: refactor
+task_id: 05-refactor
+required_artifacts:
+  - path: .prodify/artifacts/05-refactor.md
+    format: markdown
+    required_sections:
+      - Behavior Guardrails
+      - Changed Files
+      - Policy Checks
+      - Selected Step
+      - Success Criteria
+allowed_write_roots:
+  - .prodify/artifacts/
+  - README.md
+  - assets/
+  - src/
+  - tests/
+forbidden_writes:
+  - .prodify/contracts/
+policy_rules:
+  - Execute exactly one selected step.
+  - Keep the diff minimal and behavior-preserving unless the plan says otherwise.
+success_criteria:
+  - The selected plan step is implemented fully.
+  - Unrelated files remain untouched.
+skill_routing:
+  default_skills:
+    - refactoring-method
+    - test-hardening
+  allowed_skills:
+    - react-frontend
+    - refactoring-method
+    - test-hardening
+    - typescript-backend
+  conditional_skills:
+    - skill: react-frontend
+      when:
+        all:
+          - fact: framework
+            includes: react
+      reason: repo framework includes React
+    - skill: typescript-backend
+      when:
+        all:
+          - fact: language
+            includes: typescript
+      reason: repo language includes TypeScript
+---
+# Refactor Contract
+
+Use this contract to record the single plan step executed, the files changed, and the guardrails that preserved behavior.

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

@@ -0,0 +1,56 @@
+---
+schema_version: 1
+contract_version: 1.0.0
+stage: understand
+task_id: 01-understand
+required_artifacts:
+  - path: .prodify/artifacts/01-understand.md
+    format: markdown
+    required_sections:
+      - Current State
+      - Open Questions
+      - Policy Checks
+      - Repository Summary
+      - Success Criteria
+allowed_write_roots:
+  - .prodify/artifacts/
+forbidden_writes:
+  - src/
+  - tests/
+policy_rules:
+  - Operate only on verified data.
+  - Preserve the existing behavior during understanding.
+success_criteria:
+  - The repository intent is captured clearly.
+  - Known unknowns are listed explicitly.
+skill_routing:
+  default_skills:
+    - codebase-scanning
+  allowed_skills:
+    - codebase-scanning
+    - maintainability-review
+    - react-frontend
+    - typescript-backend
+  conditional_skills:
+    - skill: maintainability-review
+      when:
+        all:
+          - fact: project_type
+            includes: cli
+      reason: repo exposes a CLI surface
+    - skill: react-frontend
+      when:
+        all:
+          - fact: framework
+            includes: react
+      reason: repo framework includes React
+    - skill: typescript-backend
+      when:
+        all:
+          - fact: language
+            includes: typescript
+      reason: repo language includes TypeScript
+---
+# Understand Contract
+
+Use this contract to describe the current repository, verified constraints, and open questions before diagnosis begins.