> For the complete documentation index, see [llms.txt](https://handbook.hackalong.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.hackalong.io/patterns/cocreation/rock-paper-scissors-proficiency.md).

# Rock, Paper, Scissors Proficiency

Participants can indicate their proficiency to other (eg: by wearing a sticker). This can also change in time.

**Rock:** coders, handy-man, everyone that would like to get their hands dirty and just build, with or without a plan.&#x20;

**Paper:**  architects, system thinkers, everyone that would like to draw, discuss and iterate on the plan of execution.

**Scissor:**  Decorators, UX designers, graphic designers, crafters, artisans, etc..  the touch that would bring what the rock and paper have created into a beautiful piece of art.&#x20;

Proficiencies can be used to form balanced and complete teams, or to organize  activities / workshops focused on a specific proficiency.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://handbook.hackalong.io/patterns/cocreation/rock-paper-scissors-proficiency.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
