Skip to content

Latest commit

 

History

History
74 lines (50 loc) · 2.26 KB

ROADMAP.md

File metadata and controls

74 lines (50 loc) · 2.26 KB

titstack roadmap

Phase 1: Portable Codex foundation

Status: Complete

Outcome

Portable global instructions, configuration, rules, local-model profiles, and skills install without replacing private Codex runtime state.

Exit criteria

  • Linux, macOS, and Windows installers support preview and timestamped backups.
  • Repository validation rejects private runtime state and malformed portable configuration.

Phase 2: Workflow alignment

Status: Complete

Outcome

The repository and reusable skills encode the complete planning, implementation, review, manual-testing, and merge workflow.

Included work

  • Add repository planning documents and reusable project templates.
  • Separate project planning from pull-request readiness.
  • Add cross-platform installer integration tests and pull-request CI.
  • Add Dependabot coverage, dependency review, and PR evidence prompts.
  • Align Claude routing and workflow documentation.
  • Use the built-in Codex review loop for local pull-request readiness checks.
  • Add explicit, cross-platform installation for selected Codex plugins without making ordinary installs mutate plugin state.
  • Render exact trusted-project entries for every Git worktree beneath the current user's ~/github directory.

Risks

  • Windows symbolic-link behavior can differ by permissions and host policy.
  • Required GitHub checks cannot be configured until their final names exist on the default branch.

Exit criteria

  • Local validation and skill validation pass.
  • Linux installer integration tests pass locally.
  • Windows installer integration tests pass in CI.
  • The final diff contains only workflow-alignment changes.

Phase 3: Enforced repository governance

Status: In progress

Outcome

GitHub settings enforce the review and validation gates documented by the repository.

Included work

  • Require pull requests and successful validation checks.
  • Require conversation resolution.
  • Require an independent approval when repository ownership makes that practical.
  • Confirm secret scanning, push protection, Dependabot, and dependency review.

Exit criteria

  • The repository ruleset protects the default branch.
  • Required checks run against the latest pull-request commit.
  • The documented merge gate matches GitHub settings.