Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion distribution.json

Large diffs are not rendered by default.

33 changes: 25 additions & 8 deletions skills/cycle/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,11 @@ a previous permission. This is an agent instruction, not a runtime cache.
the first checkpoint or a Git/session transition; it governs reporting safeguards,
not an up-front load of response templates. For a UI checkpoint apply [the checkpoint example](assets/checkpoint-example.md).

For an explicitly requested Skill evaluation in a source checkout, read
[evaluation piloting](references/session-evaluation.md) before launching runs.
Pilot the official Skill Creator CLI from the session; use its Goose runner
by default. Keep native delegation optional and evaluation separate from product acceptance.

Verify available filesystem, shell/test and delegation capabilities. Read the
project's local instructions and inspect the repository without mutation first.
Ask only for missing information that blocks safe progress; list nonblocking
Expand All @@ -64,6 +69,9 @@ a previous permission. This is an agent instruction, not a runtime cache.
Before creating or repairing task descriptions or acceptance criteria, apply
[ticket authoring](references/ticket-authoring.md); verify readable purpose,
criteria, ordered inputs and restart context without duplicating execution history.
Require explicit delivery mechanisms and asset maps for ready implementation work.
Route changed scope through consolidated ticket sections and reconciled dependency
edges; a populated tracker record alone does not prove execution readiness.

If the repository uses Beads, apply [the Beads integration](references/beads-integration.md)
before choosing work or mutating task state. Use fresh `bd prime` guidance;
Expand Down Expand Up @@ -101,18 +109,23 @@ a previous permission. This is an agent instruction, not a runtime cache.
when persisting or recovering a slice artifact or preparing a handoff, not for ordinary
investigation.

- Identify the approved objective, roadmap source, milestone/epic/US and smallest
reviewable slice. If there is no roadmap, propose one and mark it unapproved.
- Inventory branch/status and pre-existing changes, capture candidate identity,
permissions and evidence. Report the starting checkpoint before mutations.
- Identify the approved objective, available roadmap/parent context and smallest
reviewable slice. Propose a missing roadmap only for requested planning or a
decision-blocking need; mark it unapproved. Otherwise report unavailable context;
do not expand a bounded investigation merely to fill hierarchy labels.
- Inventory branch/status, pre-existing changes, permissions and evidence. For
source-only observations record inspected revision/paths, dirty state and limits;
use preliminary or exact-candidate provenance only when the check's purpose
requires it. Report the starting checkpoint before mutations.
- Keep required durable state in the agreed tracker or explicitly authorized
workspace. Do not invent a default directory; verify the destination, conflicts
and permission before writes. Do not persist private secrets, tokens, full sensitive tool outputs,
or unnecessary personal data. If persistence is unavailable, emit a copyable
handoff and disclose that no durable state was written.
- Resume at the first incomplete or invalidated phase, not from the beginning.
Reinspect the working tree and compare candidate identity; treat old evidence
as stale if related files or environment changed.
Reinspect the working tree and select source-only observation, preliminary
check or exact-candidate proof under candidate identity; compare exact inputs
before proof reuse. Treat old evidence as stale if related files or environment changed.

Treat roadmap outcomes, epic capabilities, user-story behavior and executable tasks
as different levels. Keep distant work coarse and detail the ready frontier only.
Expand All @@ -136,7 +149,11 @@ a previous permission. This is an agent instruction, not a runtime cache.
safe actions without repeatedly asking. Request a real decision for unresolved
trade-offs. A branch covers a US or slice, not necessarily a single task.

Use delegation only if available and useful. Give each worker the objective,
Use delegation only if available and useful, subject to required isolation or
independence. Coordinator baseline verification and bounded questions from
sufficient available sources need no worker; deeper Research investigations
follow that phase's dispatch policy.
Give each worker the objective,
acceptance criteria, contract, approved scope, input artifacts and exclusive
writable paths. Workers cannot coordinate implicitly. Parallel writers must
never share a file. Workers return result, exact changes, evidence, limitations
Expand Down Expand Up @@ -194,7 +211,7 @@ a previous permission. This is an agent instruction, not a runtime cache.

- Verify the active objective/task, product-context coverage and freshness, current candidate, permissions and first incomplete or invalidated phase; retain the routing rationale and unmet prerequisites.
- Prepare the immediate next action and blockers within current scope/permissions; collect handoff inputs, distinguishing recommendations from performed actions; format them after the output-contract application below.
- After investigation and before drafting any user-facing phase response (including blocked or unchanged results), apply [the common output contract](references/common-output.md) and [this phase's delivery contract](references/requirements-output.md); apply their checklists and five-section report.
- After investigation and before drafting any user-facing phase response (including blocked or unchanged results), apply [the common output contract](references/common-output.md) and [this phase's delivery contract](references/requirements-output.md); apply their checklists and selected delivery form (compact when eligible, otherwise five-section report).

Apply [the commit report](references/commit-report.md) only for a proposed,
performed, failed or externally observed commit. Apply
Expand Down
16 changes: 13 additions & 3 deletions skills/cycle/references/candidate-identity.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,19 @@
# Candidate identity v1.2.0
# Candidate identity v1.3.0

Contract ID: agentic-development/candidate-identity
Contract version: 1.2.0
Contract version: 1.3.0

Use before planning checks, freezing a candidate or reusing evidence. Choose one path.
Use before planning checks, freezing a candidate or reusing evidence. Choose the
path matching the purpose; source reading alone is not an acceptance check.

## Source-only observation

Record inspected paths/sections, revision or file identity, current dirty state and
provenance limits. For bounded source reading, no capture CLI or full manifest is
required. Do not imply executed behavior, complete input coverage or exact-candidate
acceptance from a revision/hash. Refresh affected conclusions when inputs change.
Preliminary executed checks use A; exact-candidate acceptance or proof reuse uses B.
Reusing a cited observation with verified freshness does not turn it into B proof.

## A. Run a preliminary check

Expand Down
31 changes: 24 additions & 7 deletions skills/cycle/references/common-output.md
Original file line number Diff line number Diff line change
@@ -1,15 +1,32 @@
# Common delivery output contract v1.3.0
# Common delivery output contract v1.4.0

Contract ID: agentic-development/common-output
Contract version: 1.3.0
Contract version: 1.4.0

Read after investigation and before drafting every user-facing phase delivery,
including blocked, unchanged and standalone results. Reuse unchanged guidance
already loaded in this context; verify it before delivery rather than rereading blindly.
This document governs response formatting, not permission to act. Requirements
must already have been resolved before the actions they govern.

## Mandatory five-section final report
## Compact bounded delivery

For a bounded read-only or no-change phase result with no actual handoff, commit,
judgment or session-end boundary, a concise Markdown response may replace the full
five-section report. Retain goal and task (or unavailable identity), actual phase,
result, evidence and limits, preservation and current authority, and next action
with its prerequisite (or an explicit stop). State actual changes or their absence;
never omit a material blocker, failure, ownership conflict or unmet criterion.
A blocked result can use this path only when the same boundary conditions hold.
No cycle visual, empty headings or YAML card is required on this path. Do not turn
an ordinary answer into a handoff/session end merely to satisfy a template.

Use the full five-section report for changed-source delivery, actual handoff,
commit, judgment or session-end boundaries, or an explicit full-report request.
An actual handoff retains the state card/restart prompt and boundary facts below;
compact delivery never waives provenance, permissions, review or tracker gates.

## Mandatory five-section final report at full-delivery boundaries

Keep these English labels and order; translate values into the user's language.
The current-goal heading includes the actual phase, not a proposed future phase.
Expand Down Expand Up @@ -43,7 +60,7 @@ proposed actions, and the next gate. Include applicable boundary facts below.>
## Report delivery and optional saving

A phase report is generated output, not an assumed existing input. Deliver its
required content inline by default inside the five-section response; for longer
required content inline by default in the selected delivery form; for longer
facts use concise evidence-bound summaries and verified accessible locators.
Beads remains task truth; report filenames suggested by a phase are optional.

Expand All @@ -69,7 +86,7 @@ and loop again belong in roadmap position, never in the step attribute.
Done covers only the requested scope, not parent, release or deployment acceptance.
A recommended transition does not execute or authorize it.

Show at least a compact cycle visual, using only evidence-backed state:
For the full report show at least a compact cycle visual, using only evidence-backed state:

~~~text
Research [reused] → Plan [active] → Implement [pending] → Test [pending] → Judge [pending]
Expand All @@ -79,7 +96,7 @@ Correction loop: Iterate → affected phase
This example is hypothetical. Use active, verified, reused, pending, blocked or
unknown as justified; loading a Skill does not verify a phase. Do not fabricate
a roadmap, task, milestone or acceptance. If roadmap identity is unavailable,
say so and show known cycle progress only, with unknowns explicit. Keep distant
say so; in the full report show known cycle progress only, with unknowns explicit. Keep distant
roadmap detail coarse; link verified task records instead of duplicating a tracker.
Explain a nonstandard transition with its reason, reused/current proof and missing
prerequisites. The next action names the immediate executable step, not a later
Expand Down Expand Up @@ -108,7 +125,7 @@ A new artifact format is not permission to create files or a competing task data
Read this contract after investigation and before drafting the response; before
delivery verify it together with the current phase delivery contract. Reuse already loaded unchanged guidance rather than reload blindly.

- [ ] Keep the five final headings in order, with the actual step in current goal, including blocked/no-change work.
- [ ] Select compact delivery only under its conditions; otherwise keep the five final headings in order with the actual step in current goal. Blocked/no-change alone does not waive a full boundary report.
- [ ] Identify the actual phase, verified task/status, goal and success criteria.
- [ ] Separate observations from proposals, unknowns and hypothetical examples.
- [ ] Report owned files separately from preserved user work; give review order and reasons.
Expand Down
11 changes: 6 additions & 5 deletions skills/cycle/references/communication-contract.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Communication contract v1.7.0
# Communication contract v1.8.0

Contract ID: agentic-development/communication-contract
Contract version: 1.7.0
Contract version: 1.8.0

Mandatory for every phase. This is an instruction contract, not a tool firewall.
Respond in the user's language. Keep evidence and decisions inspectable; do not
Expand All @@ -24,16 +24,17 @@ Use a full checkpoint at commit boundaries, judgment, session handoff, US closur
session start, objective change, and slice completion. Do not repeat an unchanged
full report after every tool call. Report discoveries that affect scope or safety
immediately. When no files changed, say so; never invent a diff for a phase.
At phase delivery and handoff use the five-section final report in common-output.md;
this supersedes the six-field envelope for final messages, not its evidence safeguards.
At phase delivery use the form selected by common-output.md; actual handoffs use
the full five-section final report.
This supersedes the six-field envelope for final messages, not its evidence safeguards.

## Required structure and notification fields

Read requirements-baseline.md before defining or changing requirements or verification,
and before implementation, for Goals/Non-goals, FR/GWT and applicable quantified NFRs.
After investigation and before drafting the phase response, read common-output.md
and this phase's requirements-output.md, directly linked from SKILL.md, for the
five-section final report. Its roadmap position contains progress and the immediate
selected delivery form. In the full report roadmap position contains progress and the immediate
next action; explanation carries evidence, limits and applicable checkpoint details.
Notify actual files, branches/commits and session recommendations truthfully.
Do not repeat unchanged detailed tables; use verified locators and concise summaries.
Expand Down
8 changes: 4 additions & 4 deletions skills/cycle/references/requirements-output.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
# Cycle output and handoff contract v1.3.0
# Cycle output and handoff contract v1.4.0

Apply this contract only to cycle. Read after investigation and before drafting the
phase response, with common-output.md directly linked from SKILL.md. Check both
before delivery. Operational requirements are separate in requirements-baseline.md.
The common five-heading Markdown envelope remains mandatory; this reference adds this phase's
The common contract selects compact delivery or the full five-heading Markdown envelope; this reference adds this phase's
content, not another final report or permission to write artifacts.

### cycle
Expand All @@ -15,8 +15,8 @@ and checked scope; parent/release gates remain separate.

Optional filename: `cycle-state.md` — not a required input or automatic write.
Deliver inline by default; save only through the common output contract’s explicit-destination,
permission and conflict checks. These topics belong inside explanation or its linked
report, not additional outer response headings.
permission and conflict checks. These topics belong in the selected delivery form or its linked
report; the full report places them in explanation, not additional outer headings.

## Phase delivery checklist

Expand Down
Loading
Loading