Skip to content

feat: skills should be created in .copilot/skills/ and prompt user to reload #353

Closed

Description

@spboyer

Problem

Skills that agents create during work are currently written to .squad/skills/. However, for Copilot to discover and use these skills in future sessions, they need to be in .copilot/skills/ — that's where Copilot's skill system looks.

Users don't know this, so skills get created but never actually become available in their Copilot session.

Proposed Changes

1. Write skills to .copilot/skills/ instead of .squad/skills/

When an agent extracts a reusable pattern and writes a SKILL.md, the target path should be:
.copilot/skills/{skill-name}/SKILL.md

Not:
.squad/skills/{skill-name}/SKILL.md

2. Prompt user to reload after skill creation

After any agent creates or updates a skill, the Coordinator should prompt the user:

📌 New skill created: {skill-name} Reload your Copilot session or run /skills reload to make it available.

This ensures the user knows the skill exists and takes action to load it.

3. Update the spawn template

The "AFTER work" section in the agent spawn template currently says:
3. SKILL EXTRACTION: If you found a reusable pattern, write/update .squad/skills/{skill-name}/SKILL.md

Should be updated to:
3. SKILL EXTRACTION: If you found a reusable pattern, write/update .copilot/skills/{skill-name}/SKILL.md

4. Migration for existing skills

For repos that already have skills in .squad/skills/, the upgrade flow should copy/move them to .copilot/skills/.

Context

  • Copilot's skill discovery reads from .copilot/skills/
  • Squad agents create skills as part of their "AFTER work" step
  • The disconnect means earned knowledge is written but never actually loaded by Copilot
  • cc @bradygaster

Impact

  • squad.agent.md — spawn template skill extraction path
  • emplates/skill.md — skill template reference
  • Agent charters that reference skill paths
  • Upgrade/migration flow

Activity

  1. 9 remaining items

  2. github-actions commented on Mar 13, 2026

    @github-actions
    Contributor

    ⚠️ No squad member found matching label squad:verbal. Check .squad/team.md (or .ai-team/team.md) for valid member names.

  3. github-actions commented on Mar 13, 2026

    @github-actions
    Contributor

    ⚠️ No squad member found matching label squad:fenster. Check .squad/team.md (or .ai-team/team.md) for valid member names.

  4. github-actions commented on Mar 13, 2026

    @github-actions
    Contributor

    📋 Assigned to EECOM (Core Dev)

    Issue: #353 — feat: skills should be created in .copilot/skills/ and prompt user to reload

    EECOM will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    EECOM, work on issue #353

  5. github-actions commented on Mar 13, 2026

    @github-actions
    Contributor

    📋 Assigned to Procedures (Prompt Engineer)

    Issue: #353 — feat: skills should be created in .copilot/skills/ and prompt user to reload

    Procedures will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    Procedures, work on issue #353

  6. bradygaster commented on Mar 15, 2026

    @bradygaster
    Collaborator

    Thanks for raising this, @spboyer! We've consolidated the skills migration work into #354, which is the full PRD covering the .squad/skills/ → .copilot/skills/ move. Closing this one as a duplicate so we can track everything in one place. Your input helped shape the direction — appreciate it! 👍

  7. bradygaster commented on Mar 15, 2026

    @bradygaster
    Collaborator

    Great suggestion — we're picking this up next session. Skills will be created in .copilot/skills/ going forward. Thanks for raising it! 🙏

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

    go:needs-researchNeeds investigationpriority:p1This sprintsquadSquad triage inbox — Lead will assign to a membertype:featureNew capability

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions