Skip to content
Skills Library
Management & product · Writing

project-bootstrap

/project-bootstrap

Draft missing ADR and FRD from verified project evidence without turning legacy behavior or stale documentation into approved requirements. TRIGGER WHEN: a project has no ADR or FRD, existing project knowledge must be bootstrapped from code, documentation or Codebase Map, or /daodan:init-project needs initial requirement records. DO NOT TRIGGER WHEN: recording one already understood decision (use adr-method), editing an existing FRD (use frd-method), or running the implementation cycle (use delivery-method).

Licence
MIT
Last repository change
27.10.2026

Assessment and security

85/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content20 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Draft missing ADR and FRD from verified project evidence without turning legacy behavior or stale documentation into approved requirements. TRIGGER WHEN: a project has no ADR or FRD, existing project knowledge must be bootstrapped from code, documentation or Codebase Map, or /daodan:init-project needs initial requirement records. DO NOT TRIGGER WHEN: recording one already understood decision (use adr-method), editing an existing FRD (use frd-method), or running the implementation cycle (use delivery-method).

Original author description

Draft missing ADR and FRD from verified project evidence without turning legacy behavior or stale documentation into approved requirements. TRIGGER WHEN: a project has no ADR or FRD, existing project knowledge must be bootstrapped from code, documentation or Codebase Map, or /daodan:init-project needs initial requirement records. DO NOT TRIGGER WHEN: recording one already understood decision (use adr-method), editing an existing FRD (use frd-method), or running the implementation cycle (use delivery-method).

How it works

  1. 1. Inventory and evidence
  2. 2. Draft and reconcile
Original SKILL.md headings · 36 lines, 234 words
SKILL.md preview
---
name: project-bootstrap
description: >
  Draft missing ADR and FRD from verified project evidence without turning legacy behavior or stale documentation into approved requirements.
  TRIGGER WHEN: a project has no ADR or FRD, existing project knowledge must be bootstrapped from code, documentation or Codebase Map, or /daodan:init-project needs initial requirement records.
  DO NOT TRIGGER WHEN: recording one already understood decision (use adr-method), editing an existing FRD (use frd-method), or running the implementation cycle (use delivery-method).
---

# Project knowledge bootstrap

Load `work-controller:work-record`, `project-delivery:adr-method` and
`project-delivery:frd-method`. Work in an owned run; generated records are drafts
and no project behavior changes.

## 1. Inventory and evidence

Detect `docs/adr/README.md` and the FRD index. Validate existing records before
using them; missing artifacts are a drafting request, not permission to invent.
Inventory documentation, source, tests and configuration. Use
`codebase-map:map-method` to validate or refresh a current completed map and
maximize structural discovery. If no current completed map exists, search and read
the source directly and record reduced structural coverage. A map is static
evidence, never a correctness verdict.

Classify each input claim as observed, documented or derived. Verify behavioral
documentation against current source and tests before using it. Contradictions
become explicit FRD conflicts or user questions. Unexercised runtime behavior is
a limitation, never a silent pass.

## 2. Draft and reconcile

Extract FRD requirements, entities, relations and exact evidence spans through
`frd-method`. Include only evidenced people, organizations, locations and
relations; uncertainty stays explicit. Draft architectural decisions only when
the evidence supports a real design choice and alternatives. Current behavior is
a candidate explanation, not an approved requirement.

Write Proposed artifacts through the helpers. Preserve source digests and manual
corrections on every later merge. Review contradictions with the user, then run
the relevant document/spec review. Only explicit approval promotes an artifact.
After implementation, reconciliation and verification use the same candidate and
merge gates as every other delivery.
Files in this package (2)
  • SKILL.md 2 KB
  • SKILL.toml 1 KB

Versions

RepositoryScoreLicence
This page · acaprino/alfio-claude-plugins85MIT
NoobyGains/godmode100MIT
Mozurok/fhorja.dev100MIT
signalcompose/claude-tools100MIT
acaprino/alfio-claude-plugins95MIT
acaprino/alfio-claude-plugins95MIT
acaprino/alfio-claude-plugins95MIT
acaprino/alfio-claude-plugins95MIT
acaprino/alfio-claude-plugins95MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version d20d1dcf763f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90frd-method
    Extract, validate, reconcile, approve, version and verify evidence-bound functional requirements documents in docs/frd/. TRIGGER WHEN: the user asks for an evidence-bound FRD, requirements and domain references must be extracted from project sources, a fresh extraction must be…
  • 100frd-method
    Extract, validate, reconcile, approve, version and verify evidence-bound functional requirements documents in docs/frd/. TRIGGER WHEN: the user asks for an evidence-bound FRD, requirements and domain references must be extracted from project sources, a fresh extraction must be…
  • 90frd
    Create or revise a Feature Requirement Document (FRD) for this repository. Use only when the user explicitly asks to create, draft, or revise an FRD or Feature Requirement Document, or explicitly invokes this skill. Do not trigger for ordinary feature implementation, new skills,…
  • 100frd-writer
    Write a Functional Requirements Document. Use when the user says "write an FRD", "functional requirements", "system requirements", "SRS", "what should the system do", "document the functional specs", "software requirements specification", "detailed requirements for engineering",…
  • 100frd-getting-started
    Produce the initial set of Feature Requirements Documents (FRDs) for a new project. Calibrates between an agile first pass (small set of must-have features only) and a waterfall first pass (comprehensive coverage). Asks how many features to draft, identifies them from the…
  • 100prd-writer
    Write or review a PRD or FRD (feature requirements document). Use when someone asks for a PRD, FRD, spec, requirements doc, user stories with acceptance criteria, or wants a PRD critiqued before engineering picks it up.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.