> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/user/pro-team-plan.md).

# 프로페셔널 팀 플랜

- [프로페셔널 팀 플랜이란?](https://docs.archisketch.com/guide/user/pro-team-plan/team-plan-intro.md): 프로페셔널 팀 플랜이란?
- [팀 플랜 구독하기](https://docs.archisketch.com/guide/user/pro-team-plan/team-plan-subscribe.md): 팀 플랜 결제부터 시작하기까지 전반적인 과정을 알려드립니다.
- [구독 및 결제 (FAQ)](https://docs.archisketch.com/guide/user/pro-team-plan/subscription-faq.md): 구독 및 결제에 관한 자주 묻는 질문은 도움말 센터로 이동했어요.
- [팀 플랜 사용 정책](https://docs.archisketch.com/guide/user/pro-team-plan/team-plan-refund.md): 프로페셔널 팀 플랜의 구독 시작·구독 취소·계정 관리·환불을 한눈에 안내해요.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archisketch.com/guide/user/pro-team-plan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.