/ousen-portable-agent-kit

This is the top-level package entrypoint for ousen-portable-agent-kit.

Use it when:

• the host platform prefers a single root skill;
• you want one command to remember first;
• you want a package-level index that explains the available child skills.

Command Map

You can use this root entrypoint as a unified dispatcher:

• /ousen-portable-agent-kit init ...
• /ousen-portable-agent-kit refresh ...
• /ousen-portable-agent-kit handoff ...
• /ousen-portable-agent-kit resume ...
• /ousen-portable-agent-kit impact ...
• /ousen-portable-agent-kit persist ...
• /ousen-portable-agent-kit install-adapters ...
• /ousen-portable-agent-kit specify ...
• /ousen-portable-agent-kit clarify ...
• /ousen-portable-agent-kit plan ...
• /ousen-portable-agent-kit tasks ...
• /ousen-portable-agent-kit implement ...
• /ousen-portable-agent-kit analyze ...
• /ousen-portable-agent-kit checklist ...

You can also use the child skills directly:

• /ousen-agentkit
• /ousen-init
• /ousen-refresh
• /ousen-handoff
• /ousen-resume
• /ousen-impact
• /ousen-persist
• /ousen-specify
• /ousen-clarify
• /ousen-plan
• /ousen-tasks
• /ousen-implement
• /ousen-analyze
• /ousen-checklist

Spec-driven development workflow order: specify -> clarify -> plan -> tasks -> analyze -> implement (checklist can run at any point once spec.md exists). See /ousen-agentkit or any individual ousen-* skill for details.

Runtime Notes

• The current skill directory is the directory containing this SKILL.md.
• Resolve KIT_ROOT in this order:
  1. if core/tools/agentkit_cli.py exists in the current skill directory, use the current skill directory;
  2. else if core/tools/agentkit_cli.py exists two levels above the current skill directory, use that parent directory;
  3. else if %USERPROFILE%/.copilot/portable-kits/ousen-portable-agent-kit/core/tools/agentkit_cli.py exists, use %USERPROFILE%/.copilot/portable-kits/ousen-portable-agent-kit;
  4. otherwise, stop and tell the user that ousen-portable-agent-kit has not been installed for Copilot yet.
• Do not depend on *.cmd wrappers in a Skill Store package. Call the Python entrypoint directly.
• If the host platform only discovers skills under skills/**/SKILL.md, treat this file as the package-level index and use skills/ousen-agentkit/SKILL.md as the canonical runtime dispatcher.

Instructions

1. Parse the first token in $ARGUMENTS as SUBCOMMAND.
2. If SUBCOMMAND is missing or is not one of init, refresh, handoff, resume, impact, persist, install-adapters, specify, clarify, plan, tasks, implement, analyze, or checklist, explain the supported commands and stop.
3. Resolve KIT_ROOT using the Runtime Notes order above.
4. Resolve the target project root:
   - If --root <path> is present in $ARGUMENTS, use that path.
   - Otherwise use the current working directory.
5. Confirm that python is available. If it is missing, tell the user to install Python 3.10+ and stop.
6. Run the canonical Python entrypoint:
   bash python "<KIT_ROOT>/core/tools/agentkit_cli.py" <SUBCOMMAND> ...
7. Summarize the generated or updated artifacts under .project-ai.
8. If the command is impact, read the generated markdown report in .project-ai/change-impact/ and summarize the directly impacted nodes and recommended checks.
9. If the command is persist, mention the created file in .project-ai/findings/ and the update to .project-ai/architecture-notes.md.
10. If the command is one of specify, clarify, plan, tasks, implement, analyze, or checklist, follow the detailed instructions in the matching skills/ousen-<command>/SKILL.md file instead of stopping at the raw CLI output - those commands only scaffold or validate files; the calling agent still has to read/write the actual spec.md/plan.md/tasks.md content with the create/edit tools.