Files
RepoFoundry/docs/project-plan.md
T
TirsvadandClaude Sonnet 5.5 d727f7ae60 Link synced milestones in the project plan
Add the Gitea milestone links (ids 43 to 45) to the Gateway Schedule after
the issue sync: MIL-001 -> #3 to #8, MIL-002 -> #9 to #14,
MIL-003 -> #15 to #20.

Refs: #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 #16 #17 #18 #19 #20

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-05 13:49:30 +08:00

4.3 KiB

Project Plan

Metadata

Key Value
ID PP-001
CrossReference BC-001, SA-001, MIL-001, MIL-002, MIL-003, US-001

Version History

Date Status Author Reviewer Change Commit
2026-10-05 Deprecated Jens Tirsvad Nielsen S02 Initial version 424f14f
2026-10-05 Accepted Jens Tirsvad Nielsen S02 Stories per phase: US-001.01 to US-001.03
Dates accepted
02875ae

Purpose

Schedule the three phases that deliver RepoFoundry (create-project.sh and its documentation) in dependency order. The Business Case sets no deadline, so the dates below are proposals for S01 to confirm.

Planning Assumptions

  • Week 1 starts 2026-10-05; the plan ends by 2026-11-13.
  • Phase length: two weeks.
  • S01 and S02 review each phase through a pull request, as described in SA-001. For now one person holds both roles.
  • The PO language is English, so no translated copies are kept.

Gateway Schedule

Gateway Document Window Decision date Owner Stories Main deliverable Milestone
Foundation MIL-001 2026-10-05 to 2026-10-16 2026-10-16 S01 US-001.01 Safe skeleton, config parsing, prompts, tests Milestone 43
Repositories and Mirror MIL-002 2026-10-19 to 2026-10-30 2026-10-30 S02 US-001.02 GitHub and Gitea repositories and the push mirror Milestone 44
Scaffold and Release MIL-003 2026-11-02 to 2026-11-13 2026-11-13 S01 US-001.03 Local project, framework, README, final review Milestone 45
@startgantt
Project starts 2026-10-05
[Foundation] starts 2026-10-05 and ends 2026-10-16
[Foundation Go/No-Go] happens 2026-10-16
[Repositories and Mirror] starts 2026-10-19 and ends 2026-10-30
[Repositories and Mirror Go/No-Go] happens 2026-10-30
[Scaffold and Release] starts 2026-11-02 and ends 2026-11-13
[Scaffold and Release Go/No-Go] happens 2026-11-13
@endgantt

Scope Coverage

Business Case scope item Gateway
Safe parsing of config.env and .env, tool checks, prompts, .gitignore MIL-001
Project name check on GitHub MIL-001
Creation of both repositories and the push mirror MIL-002
Partial-failure reporting MIL-002
Local directory, remotes, framework submodule, skills, hooks, templates, plan gate MIL-003
README and SSH prerequisite documentation MIL-003

Dependencies

MIL-001 → MIL-002 → MIL-003

A No-Go moves every later date by the time needed to rework the failed criteria.

Plan Risks

Risk Impact Mitigation
No disposable GitHub organization for testing Organization-owner path untested Agree the test owners before MIL-002 starts
Gitea API behaviour differs from the swagger on the live server Mirror task takes longer Test against git.tirsystem.com early in MIL-002

Open Issues

  • Decided: the proposed dates are accepted with this plan (S01 asked for its acceptance on 2026-10-05); a change needs a new Version History row.
  • Decided: origin uses HTTPS derived from GITEA_URL, unless the SSH test passed, in which case it uses SSH on port 10022.
  • Decided: use case UC-001 "Create a new project" is created, with SSD-001; tasks that implement its steps reference it.
  • Decided: S01 and S02 are both held by one person for now.
  • Open: this plan says the script does not make the first commit; confirm before MIL-003 starts.