teddy-cli 0.1.17.dev1193__tar.gz → 0.1.17.dev1199__tar.gz

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: teddy-cli
-Version: 0.1.17.dev1193
+Version: 0.1.17.dev1199
 Summary: A local-first, file-based AI coding workflow that applies the UNIX philosophy to AI collaboration.
 Author: Raphael Atteritano
 License: AGPL-3.0-only

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1193"
+version = "0.1.17.dev1199"
 description = "A local-first, file-based AI coding workflow that applies the UNIX philosophy to AI collaboration."
 authors = [{ name = "Raphael Atteritano" }]
 license = { text = "AGPL-3.0-only" }

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/src/teddy_executor/__main__.py

@@ -285,10 +285,23 @@ def config():
     typer.echo(status)
 
 
+@init_app.command()
+def templates():
+    """
+    Overwrites bundled Markdown templates in docs/templates/ with defaults.
+    """
+    from teddy_executor.core.ports.inbound.init import IInitUseCase
+
+    container = get_container()
+    init_use_case = container.resolve(IInitUseCase)
+    status = init_use_case.ensure_templates_initialized(overwrite=True)
+    typer.echo(status)
+
+
 app.add_typer(
     init_app,
     name="init",
-    help="Initialize .teddy directory, prompts, or configuration.",
+    help="Initialize .teddy directory, prompts, configuration, or templates.",
 )
 
 

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/src/teddy_executor/core/ports/inbound/init.py

@@ -13,7 +13,8 @@ class IInitUseCase(ABC):
         files are present in the current project root.
 
         Returns:
-            A human-readable summary string (e.g., "Config: unchanged. Prompts: updated (3 files).").
+            A human-readable summary string (e.g., "Config: unchanged.
+            Prompts: updated (6 files). Templates: updated (11 files).").
         """
         pass
 

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/src/teddy_executor/core/services/init_service.py

@@ -225,14 +225,19 @@ class InitService(IInitUseCase):
         Ensures the .teddy directory and default files are present.
 
         Returns:
-            A human-readable summary string (e.g., "Config: unchanged. Prompts: updated (3 files).").
+            A human-readable summary string (e.g., "Config: unchanged.
+            Prompts: updated (6 files). Templates: updated (11 files).").
         """
         if not self._file_system.path_exists(".teddy"):
             self._file_system.create_directory(".teddy")
 
         config_status = self._init_config_dir(overwrite=False)
         prompts_status = self._init_prompts(overwrite=False)
-        return f"Config: {config_status}. Prompts: {prompts_status}."
+        templates_status = self._init_templates(overwrite=False)
+        return (
+            f"Config: {config_status}. Prompts: {prompts_status}. "
+            f"Templates: {templates_status}."
+        )
 
     def ensure_prompts_initialized(self, overwrite: bool = True) -> str:
         """

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/src/teddy_executor/resources/config/prompts/architect.xml

@@ -8,6 +8,7 @@
   <instructions>
     <workflow>
       <phase_tracking>The phases below are tracked in the State Dashboard. Use these exact phase names in the dashboard's PHASES list.</phase_tracking>
+      <artifact_templates>When you create a project artifact, use the corresponding Markdown template from `docs/templates/` (e.g., `specification-document.md`, `vertical-slice.md`, `case-file.md`). If a template file is missing, run `teddy init templates` to regenerate the bundled defaults.</artifact_templates>
 
       <phase n="1" name="Exploration">
         <goal>Gather context, audit the environment, and identify all technical/functional debt.</goal>

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/src/teddy_executor/resources/config/prompts/assistant.xml

@@ -9,6 +9,7 @@
     <workflow>
       <description>The Fast Iterative Execution Loop for tactical tasks.</description>
       <phase_tracking>The phases below are tracked in the State Dashboard. Use these exact phase names in the dashboard's PHASES list.</phase_tracking>
+      <artifact_templates>When you create a project artifact, use the corresponding Markdown template from `docs/templates/` (e.g., `task-brief.md`, `specification-document.md`, `vertical-slice.md`). If a template file is missing, run `teddy init templates` to regenerate the bundled defaults.</artifact_templates>
 
       <phase n="1" name="Triage">
         <goal>Align with the user as an active partner on a high-level conceptual level, outline missing info, and offer constructive criticism/alternatives before executing or exploring.</goal>

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/src/teddy_executor/resources/config/prompts/developer.xml

@@ -13,6 +13,7 @@
     <workflow>
       <description>The Iterative Delivery Cycle. You MUST execute this full cycle (including VCP) for EACH individual deliverable separately.</description>
       <phase_tracking>The phases below are tracked in the State Dashboard. Use these exact phase names in the dashboard's PHASES list.</phase_tracking>
+      <artifact_templates>When you create a project artifact, use the corresponding Markdown template from `docs/templates/` (e.g., `vertical-slice.md`, `case-file.md`, `task-brief.md`). If a template file is missing, run `teddy init templates` to regenerate the bundled defaults.</artifact_templates>
 
       <phase n="1" name="Orientation">
         <goal>Foundation and scope verification.</goal>

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/src/teddy_executor/resources/config/prompts/pathfinder.xml

@@ -9,6 +9,7 @@
     <workflow>
       <description>The Goal-Oriented Discovery Framework to identify the optimal strategic path and produce the required artifacts for execution.</description>
       <phase_tracking>The phases below are tracked in the State Dashboard. Use these exact phase names in the dashboard's PHASES list.</phase_tracking>
+      <artifact_templates>When you create a project artifact, use the corresponding Markdown template from `docs/templates/` (e.g., `specification-document.md`, `milestone.md`, `task-brief.md`). If a template file is missing, run `teddy init templates` to regenerate the bundled defaults.</artifact_templates>
 
       <phase n="1" name="Triage">
         <goal>Align with the user as an active partner on a high-level conceptual level, outline missing info, and offer constructive criticism/alternatives before planning or exploration.</goal>

{teddy_cli-0.1.17.dev1193 → teddy_cli-0.1.17.dev1199}/src/teddy_executor/resources/config/prompts/prototyper.xml

@@ -9,6 +9,7 @@
     <workflow>
       <description>The Evolving Slice Loop. You receive a draft Vertical Slice and iteratively evolve it into a finalized, buildable plan by first empirically verifying the behavioral gap and fix with a minimal reproduction and shadow file, then validating behaviors in your sandbox.</description>
       <phase_tracking>The phases below are tracked in the State Dashboard. Use these exact phase names in the dashboard's PHASES list.</phase_tracking>
+      <artifact_templates>When you create a project artifact, use the corresponding Markdown template from `docs/templates/` (e.g., `vertical-slice.md`, `specification-document.md`, `component-design.md`). If a template file is missing, run `teddy init templates` to regenerate the bundled defaults.</artifact_templates>
 
 
      <phase n="1" name="Triage">