Exercise: Scale institutional knowledge using Copilot Spaces

[github-actions]

Scale institutional knowledge using Copilot Spaces

👋 Hey there @angelo102! Welcome to your Skills exercise!

Use Copilot Spaces to share, update, and add content for a central knowledge base

---

✨ This is an interactive, hands-on GitHub Skills exercise!

As you complete each step, I’ll leave updates in the comments:

• ✅ Check your work and guide you forward
• 💡 Share helpful tips and resources
• 🚀 Celebrate your progress and completion

Let’s get started - good luck and have fun!

_{— Mona}

[github-actions]

Step 1: Create and prime your Copilot Space

In this step you will establish a Copilot Space and give it the minimum context it needs to act as a project management knowledge hub for OctoAcme.

How does using Spaces affect my usage?

Questions you submit in a space count as Copilot Chat requests.

• If you're a Copilot Free user, this usage counts toward your monthly chat limit.

• If you use Spaces with a premium model, this usage counts toward your premium usage quota. Every question you submit to a premium model counts as one premium request, multiplied by the model's multiplier. For information about the multipliers applied to each model, see Requests in GitHub Copilot.

• Use Copilot Spaces

📖 Theory: Using Copilot Spaces as a Knowledge Hub

GitHub Copilot Spaces enables teams to centralize and democratize organizational knowledge by providing a collaborative environment for storing, searching, and refining process documentation. By connecting your repository as a source, Copilot Spaces can index your documentation and issue templates, making them easily accessible and actionable for all team members. This approach reduces single-person dependency risk, accelerates onboarding, and ensures that project management processes are consistent and repeatable.

To get started, you need access to Copilot Spaces and a GitHub Copilot plan with premium request units. Each prompt in a Space counts toward your usage quota, so be mindful of your plan's limits. For more details, see GitHub Copilot plans and Copilot Requests.

Note

Questions you submit in a Copilot Space count as Copilot Chat requests. Premium models multiply usage. See Requests in GitHub Copilot for details.

⌨️ Activity: Create your OctoAcme Project Management Hub Copilot Space

1. Navigate to GitHub Copilot Spaces https://github.com/copilot/spaces (ensure you have access to this feature)

2. Click Create Space button

3. Name your Space:

   OctoAcme Project Management Hub
   

4. Click Save

   

Add a description:

Centralizing and democratizing project management knowledge for the OctoAcme organization

⌨️ Activity: Add instructions to your Copilot Space

• In your newly created Copilot Space, look for the Instructions button

• Add the following instructions to provide context about the repository and its purpose

  

• Click Save

  ## Program process documents
  
  - Stored in `docs/`
  
  ### Purpose of this Copilot Space
  
  - Centralize scattered project management knowledge in Copilot Spaces
  - Convert tacit team insights into searchable, versioned artifacts
  - Give all team members equal access to processes, decisions, and rationale
  - Connect a repository as a structured knowledge source
  - Extract, refine, and standardize workflows collaboratively
  - Feed validated improvements back into living documentation
  - Accelerate onboarding and reduce single-person dependency risk
  - Enable consistent, repeatable project execution
  
  ## Issue templates for program process documents
  
  - Stored in `.github/ISSUE_TEMPLATE/`

⌨️ Activity: Add your cloned repository as a source repository to your Copilot Space

1. In your newly created Copilot Space, look for Add sources button

2. Add this exercise repository as a source:

   • Copy and paste your GitHub repository for this exercise called out below.

   • You can also type the name in the search and it will come up as well or copy/paste the name below.

     angelo102-learning/skills-scale-institutional-knowledge-using-copilot-spaces
     

   • This gives Copilot access to the project management documentation and processes in the repository

3. Select the docs and the .github/ISSUE_TEMPLATE folders

4. Verify the repository appears in your sources list

⌨️ Activity: Create an issue in the repository for a README for OctoAcme Project Management Docs

• Open your Copilot Space you created above. https://github.com/copilot/spaces

• In the conversation interface prompt the following:

  

  Create an issue in the repository angelo102-learning/skills-scale-institutional-knowledge-using-copilot-spaces for a README for OctoAcme Project Management Docs
  that has links to all the docs in the docs folder.
  - The README should also contain a brief summary of the project management processes used by OctoAcme.
  - Make sure README, project management processes summary, and links are in the title of the issue.
  - Use the "Add Content to Project Management Process Docs" template.
   - Which process document do you want to update? "<new document>"
   - Fill in the other fields
  

You can then add this issue to your repository by clicking the Create button.

📷 Show screenshot of the issue draft

You can copy or open the link in a new tab to see the newly created issue

📷 Show screenshot of the created issue

Having trouble? 🤷

• Make sure you have access to GitHub Copilot Spaces (currently in beta/limited access)
• The repository should be publicly accessible for Copilot to index it
• If you can't access Copilot Spaces, you can continue by manually exploring the repository structure and documentation
• Repository indexing can take seconds to minutes depending on size

[github-actions]

Please, follow the steps above.
I'll watch your progress in the background to provide feedback. 🧐

[github-actions]

🎉🎉🎉 Nice work! Everything is perfect! 🎉🎉🎉
Preparing content for step 2! One moment... 🤓

[github-actions]

Step 2: Explore & summarize project management processes and create a README

In this step you will:

• Explore the process docs in the docs/ folder (e.g., project-lifecycle.md, roles-responsibilities.md, communication-plan.md)
• Generate a 3–4 paragraph summary in your Copilot Space (workflows, roles, communication, quality)
• Use that summary to create/attach the existing issue about the README
• Create a pull request adding a README that links all process docs and includes the brief overview

📖 Theory: Attaching issues and assigning to the GitHub Copilot coding agent

While reading, note:

• End-to-end workflow stages and handoffs
• Defined roles/personas and responsibilities
• Decision / escalation points
• Communication cadences and channels
• Quality gates, reviews, and acceptance criteria

You will use the prompts below to:

1. Summarize the docs
2. Attach the prior issue
3. Generate a PR adding a docs/ README with links + overview

Proceed to the activities and run the provided prompts in your Copilot Space.

⌨️ Activity: Explore the project management process docs and Summarize in your Copilot Space

• Generate a summary. Should be 3-4 paragraphs covering the main processes OctoAcme uses for project management.

• Open your Copilot Space you created in the previous step. https://github.com/copilot/spaces or by clicking the name

• Start a new conversation in the Copilot Space and prompt the following:
  

  

  - Create a 3-4 paragraph summary of the project management processes used by OctoAcme
    based on the documentation in the docs folder of this repository.
  - Focus on key workflows, personas/roles, communication strategies, and quality assurance practices.
  

📷 Show screenshot of the conversation output

⌨️ Activity: Attach an issue and create a pull request for the Copilot coding agent

In this activity, you will connect the issue you created in Step 1 to your Copilot Space conversation and use the coding agent to automatically create a pull request.

1. Find your issue number: Go to https://github.com/angelo102-learning/skills-scale-institutional-knowledge-using-copilot-spaces/issues and note the issue number from Step 1 (it should be about creating a README for project management docs)

2. Attach the issue to your conversation: In your Copilot Space, type the following (replace # with your actual issue number):

Important

After typing the issue reference below, press <SHIFT> + <ENTER> to add it to the conversation without sending the message yet.

@angelo102-learning/skills-scale-institutional-knowledge-using-copilot-spaces/issues/#

(Example: if your issue is #2, type @angelo102-learning/skills-scale-institutional-knowledge-using-copilot-spaces/issues/2)

1. Verify the issue is attached: You should see the issue title and details appear in your conversation

2. Create the pull request: Now send this prompt to create the pull request:

   

   

   - Using the github-coding-agent tool create a pull request based on the attached issue.
   - The README should also contain a brief overview of the project management processes
     used by OctoAcme based on the summary we just created.
   - The README should be in the `docs/` folder
   - Add this pull request to the attached issue.
   - Add angelo102 as a reviewer for the pull request
   

3. Allow the coding agent: When prompted, select Allow to let the coding agent work on your repository

   

4. Monitor progress: You should receive a notification that the Copilot coding agent is working on your pull request.

   There are two ways you can check the status of the coding agent working on your pull request

   1. Go to your repository and click Pull requests to see the progress:

      

   2. You can track progress and view details in Mission Control for agent tasks by following the task link

      

5. Check open pull requests: We can check pull request status from our Copilot Space as well.

   

   check open pull requests
   

   

Note

The coding agent typically takes 5-15 minutes to complete the work. You can click View session to watch the progress if desired.

1. Review and merge: Once the pull request is ready:

   a. Submit review: Leave a comment (optional), click Approve, then Submit review

   

   b. Merge: Select Ready for review, then Merge pull request and Confirm merge

   

Having trouble? 🤷

• Can't find your issue? Check the Issues tab in your repository for the issue you created in Step 1
• Issue not attaching? Make sure you're using the exact format @angelo102-learning/skills-scale-institutional-knowledge-using-copilot-spaces/issues/# where # is your issue number
• Coding agent not working? Ensure you have the necessary permissions to create pull requests in your repository
• Pull request creation failed? The issue must be properly attached before the coding agent can work on it

[github-actions]

Please, follow the steps above.
I'll watch your progress in the background to provide feedback. 🧐