Skip to content
active platform v0.2.0 New Ideas and Technology Plans Created 2026-06-17 · Updated 2026-07-24

MINT — New Ideas and Technology Plans

  • Product: New Ideas and Technology Plans
  • Family: Meta

Objective

Provide a structured, version-controlled repository for plans, product proposals, and technology ideas — enabling collaborative development of initiatives from concept through execution with AI agent assistance.

Context

Planning artifacts (product proposals, architecture decisions, ideas, initiative scoping) are currently scattered across Google Docs, Confluence pages, Slack threads, and individual notes. There's no single place where plans are:

  • Version-controlled with full history
  • Structured consistently for quick scanning
  • Accessible to AI agents for drafting and iteration
  • Shareable via the repository itself
  • Indexed with status tracking

MINT is a git repository where each markdown file represents one plan. AI agents (primarily Kiro) assist with research, drafting, and iteration.

Tools In Use

  • GitHub (repository hosting and sharing)
  • GitHub Actions (README generation, plan validation, pre-commit)
  • Python via uv (PEP 723 standalone scripts for index generation and validation)
  • prek (pre-commit hook runner — formatting and conventional-commit enforcement)
  • Kiro (AI agent for research, drafting, and iteration)
  • oprah-product-map (authoritative product, key, and family values)

Scope

In scope

  • GitHub repository for plans, proposals, and ideas
  • AGENTS.md defining structure, conventions, and agent behavior
  • A single plan template (TEMPLATE.md) covering frontmatter schema and standard sections
  • Auto-generated README index of all plans with status, product, domain, and tags
  • Frontmatter validation, including reconciliation against the product map
  • Document lifecycle and archival workflow

Out of scope

  • Approval workflows or gate processes
  • Integration with project management tools (Jira, etc.)
  • Automated notifications on plan changes

Repository Structure

/
├── README.md              # Auto-generated index (do not edit manually)
├── AGENTS.md              # Conventions, templates, agent behavior
├── TEMPLATE.md            # Plan template for new files
├── Jenkinsfile            # Pipeline definition
├── scripts/
│   ├── generate-readme.py # README index generator
│   └── validate-plans.py  # Frontmatter + product map validator
├── .github/workflows/     # README generation, plan validation, pre-commit
├── 2026/                  # Plans created in 2026
│   └── *.md
└── archive/               # Completed, cancelled, or retired plans

Plans are partitioned by the year in their created frontmatter field. This caps directory size without requiring category decisions, and the validator enforces that a plan's directory matches its created year. Discovery is by search and by the generated index rather than by browsing.

Document Lifecycle

Statuses, transitions, and archival rules are defined once in AGENTS.md and deliberately not duplicated here — a second copy of the state machine drifts from the first.

Risks

Risk Likelihood Impact Mitigation
Plans go stale without updates Medium Low Status field and changelog make staleness visible
Over-reliance on AI for plan substance Low Medium Human provides direction and decisions; AI assists with research and structure

Success Criteria

  • Repository exists with AGENTS.md, README index, and template
  • New plans can go from idea to structured draft in a single agent session
  • Others can read a plan and understand scope, status, and open questions in under 2 minutes

Open Questions

  • mint is registered as product_type: Placeholder in the product map. Does it stay a placeholder, or get promoted to a full product entry?

References

Decisions

Date Decision Rationale
2026-06-17 Partition plans into year directories from the created field Caps directory size without requiring category decisions that invite disputes
2026-06-17 One template, not three (idea / initiative / full) Sections are explicitly optional, so a single template covers lightweight and heavyweight plans; three templates would need three sets of conventions
2026-06-17 README is generated, never hand-edited Removes the drift between the index and the plans it indexes
2026-06-17 Merge authority is CODEOWNERS, not a separate approver list Uses the mechanism GitHub already enforces rather than a convention nobody can enforce

Changelog

Date Status Change
2026-06-17 draft Initial draft
2026-07-24 active Review pass: replaced the stale repository structure with the actual layout; removed the duplicated document lifecycle in favor of AGENTS.md; corrected Tools In Use and Scope to what was built; removed answered open questions and recorded them as decisions; added References