Дизайн-документ для фичи в кодовой базе

★ 6.9 · vibe-coding

Feature Design Document is a Claude Code skill that guides users through a four-phase cycle for authoring a design document grounded in the actual codebase: Explore & Interview → Draft → Resolve open questions → Iterate. Reach for it when you need to write an RFC or feature spec before touching code; when architectural decisions are unclear and you want open questions captured formally; when a feature spans several modules and scattered notes won't cut it. During exploration the skill reads README.md, CLAUDE.md, and ARCHITECTURE.md, searches related files with Grep and Glob, queries crosslink knowledge, and checks existing drafts in .design/; it then asks 3–5 clarifying questions, each anchored to a concrete file or pattern found in the codebase. The draft is written to .design/<slug>.md with a fixed structure: Summary, Requirements, Acceptance Criteria, Architecture, Open Questions, and Out of Scope. Unresolved ambiguities become OPEN HTML-comment blocks and are worked through interactively. After writing, a validation checklist runs and the document is stored in crosslink knowledge. Arguments --issue, --gh-issue, and --continue let you start from a tracked issue or resume an existing draft. Best suited for teams using the crosslink CLI; not applicable for projects without a codebase or where the .design/ directory and crosslink toolchain are unavailable.