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).
- Author
- acaprino ↗
- Repository
- alfio-claude-plugins ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
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. Inventory and evidence
- 2. Draft and reconcile
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). --- <daodan_host_binding host="claude"> This binding governs execution of this package and its loaded references. It takes precedence over executable examples written for another host. Use only registered tools and their actual input schema; an example never creates a tool, argument, permission, model alias or nested worker capability. Preserve the generated worker allowlist, dependency closure, scope and delivery contracts. Claude binding: repository tools are Read/Glob/Grep and Write/Edit; shell execution uses Bash and network fetch uses WebFetch. Pass the executable string in Bash's command field, and use its registered timeout/background schema. Worker dispatch uses the available native Agent mechanism and its registered agent-selection and prompt fields. Do not turn a prose role label into an invented role argument. Inherit the session model unless the declared workflow and active schema permit an override. Load installed skills by qualified ID; named roles use their owning plugin's agent identity, while workflow entries use /<plugin>:<workflow>. Required foreign providers use Claude's marketplace/install commands: claude plugin marketplace add <source>, then claude plugin install <provider>@<marketplace>. A provider that is installed but disabled is enabled with claude plugin enable <provider>@<marketplace>; check `claude plugin list --json` before the first phase, and stop with that command when any plugin of this package's dependency closure, direct or transitive, is off. A declared package MCP server is configured through the generated MCP manifest; still check its tools are actually available in the active session. The executing agent and its coordinator own continuation, recovery, verification and delivery. Skills supply knowledge and method instructions; they are not executors or a runtime persistence mechanism. Resolve each component by kind and exact installed identity. A role is dispatched as a worker, a skill loads instructions, and a workflow starts its declared method. Kernel owner-qualified skill references are logical provider identities: resolve them to the actual host registry name and verified installed provider path. Do not invent a registry string by adding an owner's prefix when the host does not use it. Do not load an agent identity as a skill or execute a workflow name as a shell command. Declared required foreign providers remain mandatory. If a required provider or capability (including required MCP access or isolation) is unavailable, stop its dependent phase and report the missing capability. Optional external providers follow the method's declared selection and absence behavior; their absence alone does not block the base workflow. Report any explicitly requested but unavailable provider contribution as unfulfilled and continue independent work. Do not install a different host's plugin or substitute unrelated skills to claim coverage. Shell execution alone does not establish interactive stdin. Before a capture or checkpoint, use an available session-control mechanism. When stdin is unavailable, keep user-driven capture in a supported background process with bounded output and an explicit stop signal controlled by the coordinator after the user's completion message. Close owned browser/process resources on completion or cancellation. Continue working within the current authorization while the requested result is achievable. After a tool error, inspect its cause, correct the relevant input or implementation, retry when justified and verify the outcome; never repeat a failing action blindly. Do not close the turn with a promise or a partial result when an authorized next step can still produce or verify the requested result. Stop only for a documented real impediment, a missing required capability, an unresolved human decision or the caller's stop request. At that boundary, report completed results, remaining work and the concrete prerequisite for continuation; continue any independent work that the blocker does not prevent. A tool's successful exit, a worker stop or an idle session is not the deliverable. Return final text naming observed findings, artifact paths, executed checks and blockers. An empty worker result is missing delivery: inspect or resume that worker when permitted, or record failure. Verify required artifacts and candidate gates before marking the requested outcome complete. This is an execution binding, not a rewrite of source examples. Preserve programming language fences, domain code and host APIs that are the subject of marketplace-ops or agent-sdk-builder. A host-as-subject API is not a tool provided to this session. Compiled binding and static checks do not prove an installed host executed a run. </daodan_host_binding> # 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 7 KB
- SKILL.toml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · acaprino/alfio-claude-plugins | 95 | MIT |
| NoobyGains/godmode | 100 | MIT |
| Mozurok/fhorja.dev | 100 | MIT |
| signalcompose/claude-tools | 100 | MIT |
| acaprino/alfio-claude-plugins | 95 | MIT |
| acaprino/alfio-claude-plugins | 95 | MIT |
| acaprino/alfio-claude-plugins | 95 | MIT |
| acaprino/alfio-claude-plugins | 95 | MIT |
| nguyenhx2/agent-harness-bootstrap | 95 | AGPL-3.0 |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 18c3af94b64d (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
- 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… - 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… - 90bootstrap-project
Set up the playbook in a new or existing repository: AGENTS.md, ADR 0001, the living docs, CI and owner tasks. Run only when the user asks.