blueprint-authoring
Draft, refine, and tidy a multi-file project blueprint under blueprint/ as the exploratory pre-foundation draft, before any docs or specification work.
- License 许可
- MIT
- 最近更新
- 2026-07-29
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- blueprint-authoring
- metadata
- { "version": "1.0.0" }
- description
- Draft, refine, and tidy a multi-file project blueprint under blueprint/ as the exploratory pre-foundation draft, before any docs or specification work.
- compatibility
- Codex and OpenCode
03 SKILL.md 正文
Blueprint Authoring
Create and maintain the project blueprint under blueprint/: the earliest,
exploratory draft that captures product intent, technical direction, scope, and
open questions before they are promoted into the docs/ foundation or into
specs/. This is the draft stage. It is allowed to be tentative and to propose
options, but every open decision must be marked as open, not silently resolved.
The blueprint is upstream of everything: docs-author later transcribes the
approved blueprint into docs/, and spec-writer turns its buildable features
into specs/.
Inputs
- The operator's product idea, notes, or an existing blueprint to refine.
- The current
blueprint/files, if any, andblueprint/README.mdfor the format. - Do not read or depend on
docs/orspecs/; the blueprint precedes them.
Blueprint format
Follow the multi-file convention documented in blueprint/README.md:
blueprint/README.mdis the index: metadata blockquote (working title, tagline, type, stack, architecture summary, estimate, status), reading order, a file-list table with section numbers, a one-paragraph summary, and an explicit status marker.- Each section file starts with a
# §n — Titleheading and a navigation line linking the previous and next sections, then cross-references other sections as[§n](file). - Code blocks that state a binding contract or algorithm are marked as binding; illustrative snippets are marked as illustration.
- Version history is accumulative: append a new version row, never rewrite past decisions. A newer version may supersede conflicting detail, but the record of the older decision stays.
Procedure
- If starting fresh, scaffold from the template files under
blueprint/, filling bracketed placeholders. If refining, read the existing blueprint in full first. - Capture, in the right section files: pitch, mental model, feature scope (MVP / stretch / later / out of scope), tech stack, architecture, data model, technical deep dives, access control, folder structure, roadmap, notable challenges, positioning, and — for anything with a user interface — UX and design intent in §16.
- Keep the
README.mdindex, reading order, and file-list table in sync with the files that actually exist. - Record every unresolved product or technical decision explicitly as an open question rather than inventing an answer. Tentative choices must be labelled tentative.
- When tidying, preserve exact numbers, version pins, thresholds, and binding contracts the source already states; do not paraphrase a precise value.
- Update the version history and the status marker to reflect the current state.
Stop conditions
Stop and ask the operator when: the product goal itself is undefined, two sources conflict on a decision that changes scope, or the request would require promoting the draft into docs/ or specs/ (that is downstream work for docs-author and spec-writer).
Scope limits
- Modify only files under
blueprint/. - Never create or edit
docs/,specs/, application code, tests, agent configuration, policies, scripts, or CI. - Never present a tentative or invented decision as settled; open questions stay visible.
- Never rewrite version history to erase a past decision.
Output
Report the exact blueprint/ files changed, the current status marker, and the list of open questions the operator must resolve before the blueprint is promoted to docs/ and specs/.
04 同仓库更多 Skills
workflow-retrospective
Improve the durable workflow when the same agent, review, test, scope, or validation failure pattern recurs; use after incidents or repeated verifier returns.
verification
Perform final independent read-only verification of acceptance criteria, review remediation, test integrity, scope, and quality-gate evidence.
ticket-authoring
Turn a reported or observed defect into one reviewable ticket under tickets/ with reproduction, evidence, impact, and closure criteria, bound to a fix version — without fixing it or rewriting it into a specification.
technical-planning
Create a read-only implementation plan from an approved specification before code changes; use for non-trivial features, bugs, migrations, and cross-module work.
skill-governance
Audit newly installed or updated agent skills as untrusted content and propose required, optional, or denied assignments to existing agent roles. Use after staging a skills.sh installation and before promoting the skill or changing agent permissions.
security-review
Adversarially review authentication, authorization, tenant isolation, sensitive data, abuse resistance, and production reliability for a completed implementation.