← ClaudeAtlas

project-spec-writerlisted

Write comprehensive project specifications, build plans, PRDs, and feature specifications for software projects, using Markdown-formatted content inside XML tags in a .md file. Use when the user wants to plan a new application, specify features for an existing codebase, or review, refine, or expand an existing specification. Also applies to requests for technical specifications, detailed requirements, 프로젝트 스펙, 기획서, 명세서, 빌드 플랜, 요구사항 정의서, 기능 스펙, or 스펙 검토/개선. Designed for AI coding agents and human developers.
thestratcore/My-skills · ★ 0 · Code & Development · score 62
Install: claude install-skill thestratcore/My-skills
# Project Specification Writer Generate detailed project specifications with Markdown-formatted content inside XML structural tags that serve as comprehensive build plans for software projects. The specs are designed to be consumed by AI coding agents or developers to build applications with minimal ambiguity. ## Modes Pick the mode that matches the request before doing anything else: | Mode | When | Instructions | |------|------|--------------| | **New project spec** | Greenfield app/service/tool idea | Workflow below | | **Feature spec** | Adding/changing features in an existing codebase | Read [references/feature-spec-mode.md](references/feature-spec-mode.md) | | **Refine existing spec** | User has a spec file to review, improve, or expand | "Refining an Existing Spec" below | ## Language Policy - Converse with the user in the user's language. - Write spec **content in Korean by default**. Keep XML tag names, code, field names, file paths, library names, env var names, and CLI commands in English — only prose is localized. Reason: the spec is reviewed by Korean readers, but identifiers must match what actually appears in code. - If the user requests another language (or the project context is clearly non-Korean, e.g. an English-speaking team), follow that instead. ## Output Format: Markdown Inside XML Apply this format to new project specs, feature specs, and refinements. Keep the existing XML root, section tags, attributes, nesting, section order, and applicabilit