
from project-architect143
Documentation-first project planning: generates SPEC, IMPLEMENTATION, TASKS, BRANDING, and a single-shot PROMPT to hand off to coding agents for execution.
Produces documentation-first project plans that turn a brief into implementation-ready files: SPECIFICATION.md, IMPLEMENTATION.md, TASKS.md, BRANDING.md, and a PROMPT.md optimized for coding agents. The workflow ensures clear handoffs and single-shot prompts for autonomous execution.
Use when planning a new project, choosing a tech stack, breaking work into discrete tasks for an agent, or generating a single-shot Claude Code prompt to execute implementation. Ideal for engineering leads, product managers, and teams using coding agents.
Designed for Claude Code and other coding-capable agents (Cursor, Codex, Gemini CLI) that can write files and ask interactive questions.
Documentation-first project planning skill with no bundled scripts. Produces SPECIFICATION.md, IMPLEMENTATION.md, TASKS.md, BRANDING.md, and a self-contained PROMPT.md for coding agents. Well-structured SKILL.md with clear phased workflow, good frontmatter, and reference file organization. No security concerns — purely conversational, no code execution.
Clean skill — no executable code, no network calls, no security issues. Strong documentation quality and clear architecture. Main limitation is dependency on Claude Code plugin conventions (AskUserQuestion tool, CLAUDE_PLUGIN_ROOT env var) which reduces portability.