eliciting-project-goals
Use when starting Phase 1 of the Beam workflow, or when a new repository needs a `plan.md` before any scaffolding, AGENTS.md, or technical spec work begins.
Use when beginning Phase 4 of the Beam workflow, or when the user asks for a technical specification, design doc, SPEC.md, docs/SPEC.md, architecture doc, or "spec the system" for a repository.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "writing-technical-spec" with this command: npx skills add Shaurya-Sethi/skillsmp-shaurya-sethi-shaurya-sethi-writing-technical-spec
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Use when starting Phase 1 of the Beam workflow, or when a new repository needs a `plan.md` before any scaffolding, AGENTS.md, or technical spec work begins.
Use when beginning Phase 3 of the Beam workflow, or when a repository has a `plan.md` and `collab_progress/` but no `AGENTS.md` at the root (or the user asks to author or refresh `AGENTS.md`).
Use when `plan.md` exists at the repository root but either `collab_progress/` or `README.md` is missing, or when the user asks to scaffold a new repository for agent-driven development.
Use when the user asks to initialize a new repository for agent-driven development, bootstrap a project harness, or set up a fresh repo for collaborative work with coding agents.