Dataface Tasks

Implement Jared layout — scripts grouping and sync-skills reconciliation

IDINFRA_TOOLING-IMPLEMENT_JARED_LAYOUT_SCRIPTS_GROUPING_AND_SYNC_SKILLS_RECONCILIATION
Statuscancelled
Priorityp3
Milestonem1-ft-analytics-analyst-pilot
Ownersr-engineer-architect

Cancelled (2026-03-25). This task is obsolete. The repo no longer needs a Jared-specific layout migration: the operator surface consolidated around tasks naming and the useful path updates landed under Converge plans and plan commands to a single task CLI surface, with the repo/tree rename completed separately in Rename master_plans directory to tasks and align CLI paths.

Problem

This was originally filed when we were experimenting with Jared as the umbrella name for the local task-manager/orchestration surface. That short-lived packaging direction included possible scripts/jared/ grouping plus sync-skills reconciliation around a Jared-specific layout.

That migration is no longer the right shape:

  • The repo standardized on tasks as the user-facing system name.
  • CLI and command consolidation shipped under the task / tasks surface instead of a Jared-specific migration.
  • The optional scripts/jared/ grouping was never adopted as the canonical direction and would now add churn without product value.

So this task should stay archived as cancelled, not implemented.

Context

  • The planning task was useful for scoping the orchestration surface, but parts of its follow-up assumed the repo would keep leaning into Jared as a filesystem/package concept.
  • The later consolidation work moved in a different direction: use tasks consistently for the task system and keep script/CLI/docs convergence tied to that naming.
  • The relevant migration value from this task has already been absorbed by:
  • converge-plans-and-plan-commands-to-a-single-task-cli-surface
  • rename-master-plans-tree-to-tasks
  • What remains here is mostly a stale placeholder for a layout experiment we did not choose.

Possible Solutions

  • A - Implement the original Jared-specific migration anyway: rejected; it would revive naming and filesystem churn that the repo has already moved past.
  • B - Recommended: cancel this task as obsolete and point readers to the completed tasks consolidation work: preserves the history without reopening a dead branch of the design.
  • C - Re-scope it into a new tasks cleanup task: unnecessary unless a fresh concrete gap appears that is not already covered elsewhere.

Plan

  1. Mark the task cancelled.
  2. Record why the work is obsolete under the tasks consolidation direction.
  3. Link to the completed tasks consolidation tasks so future readers follow the real implementation path.

Implementation Progress

  • 2026-03-25: Cancelled as obsolete. The repo standardized on the tasks surface instead of a Jared-specific layout migration.
  • converge-plans-and-plan-commands-to-a-single-task-cli-surface covers the command/CLI consolidation that this task would otherwise have touched.
  • rename-master-plans-tree-to-tasks covers the repo/tree rename and broad path convergence that made a Jared-specific grouping task unnecessary.

QA Exploration

  • [x] QA exploration completed (or N/A for non-UI tasks)

N/A — cancelled infrastructure/task-metadata cleanup.

Review Feedback

  • [ ] Review cleared