@harness-forge/cli 0.1.0

package/templates/workflows/implement-perl-change.md

@@ -0,0 +1,175 @@
+---
+id: implement-perl-change
+kind: workflow-template
+title: Implement Perl Change
+summary: Deliver Perl work using the promoted common guidance, language rules, and structured language pack.
+mode: sequential
+status: stable
+version: 1
+applies_to:
+  - codex
+  - claude-code
+languages:
+  - perl
+supported_targets:
+  - codex
+  - claude-code
+supported_languages:
+  - perl
+default_agents:
+  - planner
+owner: core
+generated: false
+---
+
+## Purpose
+
+Deliver a Perl change with explicit use of the promoted rules, structured references, and validation steps.
+
+## When to Use
+
+Use when the dominant task language is Perl or when the touched files match the shipped perl pack.
+
+## Entry Conditions
+
+- the affected files are known
+- the dominant language is Perl
+- `rules/common/` and the matching language rule directory are available
+
+## Workflow Stages
+
+### Stage 1: Orient
+
+**Goal**
+Load the common guidance and the Perl-specific references relevant to the task.
+
+**Consumes**
+- `rules/common/`
+- `skills/perl-engineering/SKILL.md`
+- `knowledge-bases/structured/perl/docs/overview.md`
+
+**Produces**
+- selected rule set
+- implementation constraints
+
+**Exit Criteria**
+- the applicable guidance is identified
+- the validation path is known
+
+**Failure Conditions**
+- the task language is mismatched
+- the structured references are unavailable
+
+**Next Trigger**
+Move to design once the active rules and examples are pinned down.
+
+### Stage 2: Design
+
+**Goal**
+Map the change to modules, boundaries, validation, and tests.
+
+**Consumes**
+- `rules/common/`
+- `rules/perl/`
+- `knowledge-bases/structured/perl/examples/01-reference-scenario.md`
+
+**Produces**
+- file touch list
+- verification approach
+
+**Exit Criteria**
+- file-level intent is explicit
+- the test or review path is clear
+
+**Failure Conditions**
+- dependencies or boundaries remain ambiguous
+- no workable validation path exists
+
+**Next Trigger**
+Move to implementation when the change is concrete enough to execute safely.
+
+### Stage 3: Implement
+
+**Goal**
+Apply the change following the promoted guidance.
+
+**Consumes**
+- selected design
+- `rules/common/security.md`
+- `rules/perl/security.md`
+
+**Produces**
+- code or script changes
+- updated docs if behavior changes
+
+**Exit Criteria**
+- the implementation matches the intended design
+- obvious safety checks are addressed
+
+**Failure Conditions**
+- the implementation diverges from the selected pattern
+- a blocking compile or runtime issue appears without a safe fix
+
+**Next Trigger**
+Move to verification after the implementation compiles or is otherwise ready to validate.
+
+### Stage 4: Verify
+
+**Goal**
+Validate behavior against the structured review and testing guidance.
+
+**Consumes**
+- `knowledge-bases/structured/perl/docs/review-checklist.md`
+- `rules/perl/testing.md`
+- repo-specific build or test commands
+
+**Produces**
+- validation results
+- release notes or follow-up tasks if needed
+
+**Exit Criteria**
+- the intended behavior is verified
+- outstanding follow-ups are captured clearly
+
+**Failure Conditions**
+- tests fail without a safe remediation path
+- the change introduces a release-blocking regression
+
+**Next Trigger**
+End the workflow or hand off follow-up tasks.
+
+## Handoff Contracts
+
+- record which `rules/common/` and `rules/perl/` files were applied
+- note the commands or manual checks used to validate the change
+
+## Exit Conditions
+
+- the implementation aligns with the promoted Perl rules and structured references
+- verification results or blockers are captured clearly
+
+## Failure Modes
+
+- changing module boundaries or package exports without checking the Perl rules first
+- finishing without running or documenting the repo's verification path
+
+## Escalation Rules
+
+- escalate when the task depends on legacy runtime constraints or unclear module ownership
+- escalate when compatibility expectations remain unresolved
+
+## Artifacts Produced
+
+- changed source files
+- validation output
+- implementation summary
+
+## Human Approval Points
+
+- approve broad module reorganizations
+- approve deviations from the promoted Perl conventions
+
+## Examples
+
+- add a Perl module method with targeted tests
+- refactor a script and package boundary using the structured reference scenario

package/templates/workflows/implement-php-change.md

@@ -0,0 +1,175 @@
+---
+id: implement-php-change
+kind: workflow-template
+title: Implement PHP Change
+summary: Deliver PHP work using the promoted common guidance, language rules, and structured language pack.
+mode: sequential
+status: stable
+version: 1
+applies_to:
+  - codex
+  - claude-code
+languages:
+  - php
+supported_targets:
+  - codex
+  - claude-code
+supported_languages:
+  - php
+default_agents:
+  - planner
+owner: core
+generated: false
+---
+
+## Purpose
+
+Deliver a PHP change with explicit use of the promoted rules, structured references, and validation steps.
+
+## When to Use
+
+Use when the dominant task language is PHP or when the touched files match the shipped php pack.
+
+## Entry Conditions
+
+- the affected files are known
+- the dominant language is PHP
+- `rules/common/` and the matching language rule directory are available
+
+## Workflow Stages
+
+### Stage 1: Orient
+
+**Goal**
+Load the common guidance and the PHP-specific references relevant to the task.
+
+**Consumes**
+- `rules/common/`
+- `skills/php-engineering/SKILL.md`
+- `knowledge-bases/structured/php/docs/overview.md`
+
+**Produces**
+- selected rule set
+- implementation constraints
+
+**Exit Criteria**
+- the applicable guidance is identified
+- the validation path is known
+
+**Failure Conditions**
+- the task language is mismatched
+- the structured references are unavailable
+
+**Next Trigger**
+Move to design once the active rules and examples are pinned down.
+
+### Stage 2: Design
+
+**Goal**
+Map the change to modules, boundaries, validation, and tests.
+
+**Consumes**
+- `rules/common/`
+- `rules/php/`
+- `knowledge-bases/structured/php/examples/01-reference-scenario.md`
+
+**Produces**
+- file touch list
+- verification approach
+
+**Exit Criteria**
+- file-level intent is explicit
+- the test or review path is clear
+
+**Failure Conditions**
+- dependencies or boundaries remain ambiguous
+- no workable validation path exists
+
+**Next Trigger**
+Move to implementation when the change is concrete enough to execute safely.
+
+### Stage 3: Implement
+
+**Goal**
+Apply the change following the promoted guidance.
+
+**Consumes**
+- selected design
+- `rules/common/security.md`
+- `rules/php/security.md`
+
+**Produces**
+- code or script changes
+- updated docs if behavior changes
+
+**Exit Criteria**
+- the implementation matches the intended design
+- obvious safety checks are addressed
+
+**Failure Conditions**
+- the implementation diverges from the selected pattern
+- a blocking compile or runtime issue appears without a safe fix
+
+**Next Trigger**
+Move to verification after the implementation compiles or is otherwise ready to validate.
+
+### Stage 4: Verify
+
+**Goal**
+Validate behavior against the structured review and testing guidance.
+
+**Consumes**
+- `knowledge-bases/structured/php/docs/review-checklist.md`
+- `rules/php/testing.md`
+- repo-specific build or test commands
+
+**Produces**
+- validation results
+- release notes or follow-up tasks if needed
+
+**Exit Criteria**
+- the intended behavior is verified
+- outstanding follow-ups are captured clearly
+
+**Failure Conditions**
+- tests fail without a safe remediation path
+- the change introduces a release-blocking regression
+
+**Next Trigger**
+End the workflow or hand off follow-up tasks.
+
+## Handoff Contracts
+
+- record which `rules/common/` and `rules/php/` files were applied
+- note the commands or manual checks used to validate the change
+
+## Exit Conditions
+
+- the implementation aligns with the promoted PHP rules and structured references
+- verification results or blockers are captured clearly
+
+## Failure Modes
+
+- changing framework or service boundaries without checking the PHP rules first
+- finishing without running or documenting the repo's verification path
+
+## Escalation Rules
+
+- escalate when the task depends on framework conventions not covered by the current pack
+- escalate when routing, DI, or migration behavior remains ambiguous
+
+## Artifacts Produced
+
+- changed source files
+- validation output
+- implementation summary
+
+## Human Approval Points
+
+- approve framework-wide configuration or architecture shifts
+- approve deviations from the promoted PHP conventions
+
+## Examples
+
+- update a controller or service class with focused validation
+- refactor a PHP module using the structured reference scenario

package/templates/workflows/implement-powershell-change.md

@@ -0,0 +1,175 @@
+---
+id: implement-powershell-change
+kind: workflow-template
+title: Implement PowerShell Change
+summary: Deliver PowerShell work using the seeded PowerShell rules, examples, and review guidance.
+mode: sequential
+status: stable
+version: 1
+applies_to:
+  - codex
+  - claude-code
+languages:
+  - powershell
+supported_targets:
+  - codex
+  - claude-code
+supported_languages:
+  - powershell
+default_agents:
+  - planner
+owner: core
+generated: false
+---
+
+## Purpose
+
+Deliver PowerShell work with explicit use of the promoted rules and seeded examples.
+
+## When to Use
+
+Use when a task touches PowerShell modules, automation scripts, CI flows, or Windows tooling.
+
+## Entry Conditions
+
+- the affected files are known
+- the dominant language is PowerShell
+- `rules/common/` and `rules/powershell/` are available
+
+## Workflow Stages
+
+### Stage 1: Orient
+
+**Goal**
+Load the PowerShell rules and seeded references relevant to the task.
+
+**Consumes**
+- `rules/common/coding-style.md`
+- `rules/powershell/coding-style.md`
+- `knowledge-bases/seeded/powershell/docs/overview.md`
+
+**Produces**
+- selected rule set
+- implementation constraints
+
+**Exit Criteria**
+- required PowerShell constraints are identified
+- an example path is chosen if one is relevant
+
+**Failure Conditions**
+- the task language is mismatched
+- the seeded references are unavailable
+
+**Next Trigger**
+Move to design once the applicable rules are pinned down.
+
+### Stage 2: Design
+
+**Goal**
+Map the change to commands, modules, automation boundaries, and tests.
+
+**Consumes**
+- `rules/common/patterns.md`
+- `rules/powershell/patterns.md`
+- `knowledge-bases/seeded/powershell/examples/`
+
+**Produces**
+- file touch list
+- verification approach
+
+**Exit Criteria**
+- automation boundaries are explicit
+- verification strategy is clear
+
+**Failure Conditions**
+- operating assumptions remain ambiguous
+- test strategy is missing
+
+**Next Trigger**
+Move to implementation when file-level changes are concrete.
+
+### Stage 3: Implement
+
+**Goal**
+Apply the change following the promoted PowerShell and common rules.
+
+**Consumes**
+- selected design
+- `rules/common/security.md`
+- `rules/powershell/security.md`
+
+**Produces**
+- script or module changes
+- updated docs if behavior changes
+
+**Exit Criteria**
+- implementation is explicit and idempotent where appropriate
+- security and validation concerns are addressed
+
+**Failure Conditions**
+- script safety regresses
+- automation behavior remains unclear
+
+**Next Trigger**
+Move to verification after implementation is complete.
+
+### Stage 4: Verify
+
+**Goal**
+Check behavior against the seeded review and testing guidance.
+
+**Consumes**
+- `rules/common/testing.md`
+- `rules/powershell/testing.md`
+- `knowledge-bases/seeded/powershell/docs/review-checklist.md`
+
+**Produces**
+- test results
+- final review notes
+
+**Exit Criteria**
+- validations are run or blockers are documented
+- the review checklist is satisfied
+
+**Failure Conditions**
+- tests fail without a safe fix
+- critical review issues remain
+
+**Next Trigger**
+Complete the workflow when verification is documented.
+
+## Handoff Contracts
+
+- record which rule files shaped the implementation
+- list the validation commands that were run
+
+## Exit Conditions
+
+- code aligns with `rules/common/` and `rules/powershell/`
+- relevant seeded examples or review notes were consulted
+
+## Failure Modes
+
+- bypassing the promoted PowerShell rules
+- shipping automation without checking review and safety guidance
+
+## Escalation Rules
+
+- escalate when the target execution environment is unclear
+- escalate when the seeded examples do not cover the required automation pattern
+
+## Artifacts Produced
+
+- changed source files
+- validation output
+- implementation summary
+
+## Human Approval Points
+
+- approve any high-impact automation behavior
+- approve any deviation from the seeded PowerShell guidance
+
+## Examples
+
+- implement a bootstrap script change using the seeded utility example
+- update a CI automation flow using the seeded admin automation example

package/templates/workflows/implement-python-change.md

@@ -0,0 +1,175 @@
+---
+id: implement-python-change
+kind: workflow-template
+title: Implement Python Change
+summary: Deliver Python work using the promoted common guidance, language rules, and structured language pack.
+mode: sequential
+status: stable
+version: 1
+applies_to:
+  - codex
+  - claude-code
+languages:
+  - python
+supported_targets:
+  - codex
+  - claude-code
+supported_languages:
+  - python
+default_agents:
+  - planner
+owner: core
+generated: false
+---
+
+## Purpose
+
+Deliver a Python change with explicit use of the promoted rules, structured references, and validation steps.
+
+## When to Use
+
+Use when the dominant task language is Python or when the touched files match the shipped python pack.
+
+## Entry Conditions
+
+- the affected files are known
+- the dominant language is Python
+- `rules/common/` and the matching language rule directory are available
+
+## Workflow Stages
+
+### Stage 1: Orient
+
+**Goal**
+Load the common guidance and the Python-specific references relevant to the task.
+
+**Consumes**
+- `rules/common/`
+- `skills/python-engineering/SKILL.md`
+- `knowledge-bases/structured/python/docs/overview.md`
+
+**Produces**
+- selected rule set
+- implementation constraints
+
+**Exit Criteria**
+- the applicable guidance is identified
+- the validation path is known
+
+**Failure Conditions**
+- the task language is mismatched
+- the structured references are unavailable
+
+**Next Trigger**
+Move to design once the active rules and examples are pinned down.
+
+### Stage 2: Design
+
+**Goal**
+Map the change to modules, boundaries, validation, and tests.
+
+**Consumes**
+- `rules/common/`
+- `rules/python/`
+- `knowledge-bases/structured/python/examples/01-reference-scenario.md`
+
+**Produces**
+- file touch list
+- verification approach
+
+**Exit Criteria**
+- file-level intent is explicit
+- the test or review path is clear
+
+**Failure Conditions**
+- dependencies or boundaries remain ambiguous
+- no workable validation path exists
+
+**Next Trigger**
+Move to implementation when the change is concrete enough to execute safely.
+
+### Stage 3: Implement
+
+**Goal**
+Apply the change following the promoted guidance.
+
+**Consumes**
+- selected design
+- `rules/common/security.md`
+- `rules/python/security.md`
+
+**Produces**
+- code or script changes
+- updated docs if behavior changes
+
+**Exit Criteria**
+- the implementation matches the intended design
+- obvious safety checks are addressed
+
+**Failure Conditions**
+- the implementation diverges from the selected pattern
+- a blocking compile or runtime issue appears without a safe fix
+
+**Next Trigger**
+Move to verification after the implementation compiles or is otherwise ready to validate.
+
+### Stage 4: Verify
+
+**Goal**
+Validate behavior against the structured review and testing guidance.
+
+**Consumes**
+- `knowledge-bases/structured/python/docs/review-checklist.md`
+- `rules/python/testing.md`
+- repo-specific build or test commands
+
+**Produces**
+- validation results
+- release notes or follow-up tasks if needed
+
+**Exit Criteria**
+- the intended behavior is verified
+- outstanding follow-ups are captured clearly
+
+**Failure Conditions**
+- tests fail without a safe remediation path
+- the change introduces a release-blocking regression
+
+**Next Trigger**
+End the workflow or hand off follow-up tasks.
+
+## Handoff Contracts
+
+- record which `rules/common/` and `rules/python/` files were applied
+- note the commands or manual checks used to validate the change
+
+## Exit Conditions
+
+- the implementation aligns with the promoted Python rules and structured references
+- verification results or blockers are captured clearly
+
+## Failure Modes
+
+- changing module or API boundaries without checking the Python rules first
+- finishing without running or documenting the repo's verification path
+
+## Escalation Rules
+
+- escalate when the task needs framework-specific behavior not covered by the pack
+- escalate when typing, dependency, or deployment constraints stay unclear
+
+## Artifacts Produced
+
+- changed source files
+- validation output
+- implementation summary
+
+## Human Approval Points
+
+- approve architecture shifts across services or package boundaries
+- approve deviations from the promoted Python conventions
+
+## Examples
+
+- add a FastAPI endpoint and verify request and response behavior
+- refactor a Python module using the structured reference scenario