Skip to content

Releases: unkos-dev/specful

v0.3.1

Choose a tag to compare

@specful-release specful-release released this 01 Sep 23:41
ff72793

Added

  • (init) retire installed instruction files (#67)

    • Stop specful init from creating or modifying agent instruction
      files.
    • Remove the retired instruction templates, repository copy, and managed
      AGENTS.md block.
    • Update the charter and public documentation to describe the delivered
      adoption boundary.

    Installed instruction files duplicated the repository configuration,
    schemas, templates, and artifact corpus, and could become a competing
    source of project authority. Agent support now remains opt-in and
    harness-side, consistent with ADR-0005, while the convention stays
    usable through ordinary repository files.

  • (plugin) add focused authoring and CLI skills (#64)

    • replace the shared authoring and adoption skills with focused
      Requirement, Design, and ADR authoring skills
    • add concise skills for validation, indexing, catalog lookup, and
      traceability without granting write authority to checks
    • align the charter and ADR with adopter-owned validation and
      substantive-review policy

    Skills should teach artifact-specific craft and make Specful operations
    available when useful without becoming canonical project policy or
    deciding how an adopting repository enforces review.

Other

  • (readme) surface the agent skills and refresh the status (#61)

    • Renames the README's Two tiers section to Agent skills and names
      the three skills (specful-author, specful-review, specful-adopt)
      with what each does, keeping the install commands and the
      defer-to-repository rule.
    • Drops the Status section: the README describes what Specful is and
      how to use it, and release maturity signalling belongs in the release
      notes.

    A reader scanning the README for agent support could miss the plugin
    entirely: the section heading did not mention skills or agents, and the
    skills were never named. The status section narrated delivery progress
    in a document that introduces the current-state writing model.

v0.3.0

Choose a tag to compare

@specful-release specful-release released this 31 Aug 12:24
c42aa9e

This release replaces the MSRS/MSDD artifact model with first-class Requirement and Design artifacts, following the
accepted ADRs SPECFUL-ADR-0002 through SPECFUL-ADR-0004. It is a direct, pre-1.0 break: there is no compatibility layer
and no automated migration. It also delivers the documentation site at https://unkos-dev.github.io/specful/ and an
opt-in agent plugin, installed from this repository's own marketplace, carrying skills for authoring, reviewing, and
adopting the convention.

Breaking changes

  • schemas/msrs/ and schemas/msdd/ are removed. schemas/requirement/v1 (type: REQ) and schemas/design/v1
    (type: DESIGN) replace them.
  • The ADR schema's discriminator moves from kind: adr to type: ADR, in place at profile-version: 1. Existing ADRs
    must update their frontmatter.
  • ADR section headings move to sentence case: Context and problem statement, Decision drivers, Considered options,
    Decision outcome (and, where present, Pros and cons of the options, More information).
  • .specful/config.yaml counters change from next-adr-sequence / next-msrs-sequence /
    next-requirement-sequence / next-msdd-sequence to next-adr-sequence / next-requirement-sequence /
    next-design-sequence. config-version stays 1.
  • specful new msrs and specful new msdd are removed. Use specful new requirement and specful new design, each
    taking --scope as before. Requirements and Designs live under docs/specs/<scope>/requirements/ and
    docs/specs/<scope>/design/ respectively (previously msrs/ and msdd/).
  • A Requirement is one normative obligation per file (Statement, Rationale, Acceptance criteria,
    More information); the old per-module bundled requirements with source citations are gone. A Design describes one
    subject across eight canonical sections (Purpose and boundaries, Structure, Interfaces and dependencies,
    Data and state, Runtime behaviour, Failure and recovery, Security and operations, More information) and
    declares the Requirements it satisfies.

Manual conversion steps for an existing repository

  1. Edit .specful/config.yaml: replace next-msrs-sequence and next-msdd-sequence with next-design-sequence, and
    rename any existing Requirement counter to next-requirement-sequence if it is not already named that.
  2. For every ADR, change kind: adr to type: ADR and update its ## headings to sentence case.
  3. For every MSRS module, split its bundled requirements into individual type: REQ files under a requirements/
    directory, one obligation per file, following templates/requirement.md.
  4. For every MSDD module, convert it to a type: DESIGN file under a design/ directory, following
    templates/design.md, and set satisfies to the Requirement identifiers it satisfies.
  5. Run specful index to regenerate the catalog and navigation views, then specful validate to confirm the result.

Added

  • (plugin) publish the first marketplace pin (#58)
  • (plugin) add the Specful agent plugin with an empty marketplace root
    (#57)
  • deliver the documentation site (#50)
  • [breaking] implement the Requirement and Design artifact model (#49)

Fixed

  • (templates) stop stamping scaffolded artifacts with an SPDX licence tag (#56)
  • (deps) update rust crate jsonschema to 0.52.0 (#47)

Other

  • adopt the Requirement and Design artifact model (#48)
  • use absolute masthead URLs in the README (#41)

v0.2.0

Choose a tag to compare

@specful-release specful-release released this 28 Aug 17:48
bc138a2

Other

  • add repository badges (#40)
  • apply Specful brand identity (#38)
  • reflow the AGENTS.md block template to fill the 120-column limit (#37)
  • [breaking] consolidate specful state under .specful (#34)
  • reflow Markdown prose to fill the 120-column limit (#35)

v0.1.2

Choose a tag to compare

@specful-release specful-release released this 27 Aug 11:14
54570a0

Fixed

  • render generated views for a zero-artifact repository (#32)

v0.1.1

Choose a tag to compare

@specful-release specful-release released this 27 Aug 06:53
a7347fe

Fixed

  • restrict the published crate to shipped content (#30)

v0.1.0

Choose a tag to compare

@specful-release specful-release released this 26 Aug 23:38
7d1238a

Added

  • add change-plan and arc-plan templates (#24)
  • install instruction content at adoption (#23)
  • discover the repository root in every command (#9)
  • answer lookup and trace queries from the catalog (#5)
  • scaffold repositories and artifacts (#3)
  • generate navigation indexes and catalog (#2)
  • implement specful validate (#1)
  • establish specful v0.1

Fixed

  • (deps) update rust crate jsonschema to 0.51.0 (#29)
  • (deps) update rust crate jsonschema to 0.50.0 (#14)
  • (deps) update rust crate saphyr-parser to 0.0.12 (#12)
  • abort index generation on collection errors (#8)

Other

  • (deps) update github/codeql-action digest to cdf488f (#28)
  • (ci) record accepted dist installer bootstrap risk (#27)
  • replace unreleased status with install instructions (#26)
  • publish release binaries with cargo-dist (#25)
  • add repository guidelines (#22)
  • (templates) drop frontmatter comment guidance (#21)
  • adopt default markdown lint rules (#20)
  • automate releases with release-plz (#18)
  • (deps) update dependency jdx/mise to v2026.8.12 (#16)
  • (deps) lock file maintenance (#17)
  • (deps) update dependency jdx/mise to v2026.8.10 (#11)
  • lint pull request titles and commits (#10)
  • add contributor process and DCO check (#4)
  • (deps) update rust to v1.98.0 (#13)
  • add issue forms and pull request template (#6)
  • adopt the justfile-driven pipeline with coverage, lint, and dependency gates (#7)
  • match rustfmt import layout