Skip to content

Add a research-project router skill #209

Description

@jerome-queck

Context

The research-project contract exists on PR #207, but the only installed academic-os skill is /learn, whose module-code discovery and Teaching-only route intentionally do not fit Research projects. Add a separate user-invoked router that reaches a synced Research-project folder from any working directory and then defers to that project’s live controls.

This issue is implemented as a stacked change on PR #207; it must not widen or rewrite /learn.

Acceptance criteria

  • A user-invoked /research-project <project identity> [-- what to work on] skill is authored at user scope in the repository, with matching Codex invocation policy.
  • The skill discovers Research-project folders under both supported macOS Google Drive mount families without reading academic-os configuration or depending on the current working directory.
  • Discovery resolves duplicate mount aliases as one folder and stops for no match or genuinely ambiguous matches.
  • Project selection can use the supplied folder name, stable key or project title from the project Definition rather than assuming one private project.
  • Every run reads the selected project’s live AGENTS.md, Project Profile and Project Definition before acting.
  • The skill routes Learning, Sources, Meetings, Research, Deliverables, Tasks and Maintenance through the project’s own named documents and asks only when the requested area is genuinely ambiguous.
  • The skill carries no copied research procedure, mathematical content, artifact format or private project identity; the Owner remains the mathematical and LaTeX author under project-local rules.
  • The design decision and machine installation instructions explain why this is a separate user-invoked route from /learn.
  • MAP and agent wayfinding name the new installed skill without changing the module Teaching route.
  • Focused tests enforce invocation, config independence, privacy and route-boundary behavior.
  • The complete repository check and test suite pass.
  • The branch is reviewed, committed with required attribution, pushed, and an open pull request is linked to this issue; nothing is merged.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agenttaskA change someone already wants made

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions