From aims-toolkit
문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서, RFC, 설계 문서, 의사결정 문서 - Collaborative document co-authoring through 3 stages: context gathering, iterative refinement, and reader testing. Use when writing docs, proposals, tech specs, decision docs, or RFCs. Do NOT use for PRD/product requirements (use prd-strategist) or implementation plans (use writing-plans).
npx claudepluginhub aimskr/aims-claude-toolkit --plugin aims-toolkitThis skill uses the workspace's default tool permissions.
Guide users through collaborative document creation via three stages.
This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.
Guides users through 3-stage workflow for co-authoring documentation: context gathering, iterative refinement, and reader testing for proposals, specs, and decision docs.
Guides users through structured workflow for co-authoring documentation via context gathering, iterative refinement, and reader testing for specs, proposals, and decision docs.
Share bugs, ideas, or general feedback.
Guide users through collaborative document creation via three stages.
Trigger conditions:
For each section:
str_replaceSection order: Start with most unknowns, leave summary for last
str_replace, never reprint whole docFor complete stage instructions, tips, and handling edge cases:
Read REFERENCE.md in this skill directory when needed.
Stage 3 Reader Testing을 통과하고 최종 문서가 사용자 승인을 받으면 완료.
User dumps a wall of text with no structure: Start Stage 1 — ask meta-context questions to organize their input into sections before attempting to structure. User wants to skip straight to writing: Confirm they have audience and purpose clear. If yes, jump to Stage 2 with their existing outline. If no, brief Stage 1. Reader testing reveals fundamental gaps: Don't patch — return to Stage 2 for the affected section. Rewrite based on new understanding.