feat(skills): integrate conditional task authoring (5by)

AGENTS.md

@@ -3,7 +3,7 @@
 ## Product
 
 - Goal: prevent scope drift, context loss and unsupported completion claims in AI-assisted software changes.
-- Product: agentic-development, seven portable Skills: cycle, research, plan, implement, test, judge, iterate.
+- Product: agentic-development, seven portable phase Skills: cycle, research, plan, implement, test, judge, iterate; plus optional task-authoring for ticket creation/repair.
 - Optional Goose hooks observe events/report structure; they are not an enforcement or acceptance engine.
 - Non-goals: automatic authorization, protected task closure, session launching or release acceptance.
 - Manifest/schema/version truth: plugin.json; do not repeat a hard-coded version here.
@@ -12,7 +12,7 @@
 
 | Path / location | Role / boundary |
 |---|---|
-| plugin.json, skills/*/SKILL.md | Source manifest and seven Skill entrypoints; required resources stay contained. |
+| plugin.json, skills/*/SKILL.md | Source manifest, seven phase entrypoints and optional task-authoring; required resources stay contained. |
 | hooks/hooks.json, scripts/observe.py | Goose-specific rules/handler in this plugin, not a second adapter. |
 | tools/production.py | Deterministic projection CLI; stdlib observer packaged as scripts/observe.pyz. |
 | tests/, integration/ | Source/handler checks and evaluation scenarios; integration/ is not an executable harness. |

CONTRIBUTING.md

@@ -103,7 +103,7 @@ suite now includes five adapted integration cases with distinct immutable
 hypothetical fixtures under skills/cycle/evals/files/. The original integration/
 inventory is retained, but is not the direct Skill Creator input. These
 explain-level cases assess proposed coordination and handoffs, not live
-implementation, tracker operations or acceptance of all seven Skills.
+implementation, tracker operations or acceptance of the seven phase Skills or optional task-authoring capability.
 
 Explanation assertions cover observable final-output properties. Actual read/order
 and prerequisite requirements remain in canonical execution_assertions metadata;

README.md

@@ -7,8 +7,7 @@ AI coding agents can lose context, drift beyond scope, and mistake passing tests
 Read the [getting started guide](https://github.com/bioinfornatics/agentic-development/blob/develop/docs/getting-started.md), then give your agent a concrete outcome:
 
 > Use Agentic Development to deliver this change: [desired behavior].
-> Clarify scope and acceptance criteria before editing. Verify the result,
-> report remaining risks, and ask before actions that need my approval.
+> Clarify scope and acceptance criteria before editing. Verify the result, report remaining risks, and ask before actions that need my approval.
 
 ## What you get
 Seven reusable Skills guide the work: six phases and one coordinator.
@@ -19,7 +18,6 @@ Goal / need → Research → Plan → Implement → Test → Judge → Scoped ac
                                   └── Iterate ←─────┘
                                       if correction is needed
 ```
-
 | Phase | Question to resolve | Expected output |
 | --- | --- | --- |
 | **Research** | What must we understand before deciding? | Cited findings, risks, unknowns, and constraints. |
@@ -33,8 +31,13 @@ Goal / need → Research → Plan → Implement → Test → Judge → Scoped ac
 Keep requirements, decisions, and restart context explicit; make small, reviewable changes; separate test results from acceptance and report missing evidence. Use the whole cycle or the phase your task needs. These are agent instructions, not an enforcement engine or a guarantee of correct software.
 
 Install: `goose plugin install https://github.com/bioinfornatics/agentic-development.git`.
-Check: `goose skills list` — only this plugin’s seven Skills, no evaluation fixtures.
+Check: `goose skills list` — the generated candidate should expose exactly eight Skills: seven phases plus optional task-authoring, no evaluation fixtures.
 Update: `goose plugin update agentic-development`. See [Goose Plugins](https://goose-docs.ai/docs/guides/context-engineering/plugins) and [Agent Skills](https://goose-docs.ai/docs/guides/context-engineering/using-skills).
+### Optional task-authoring capability
+The seven development phases remain Cycle, Research, Plan, Implement, Test, Judge and Iterate. `agentic-development:task-authoring` creates or repairs readable tickets from established scope and returns verified tracker readback or an explicit proposal.
+Load it conditionally through the host's Skill loader only for creation/repair, not routine reads, claims, updates or closure. It stops and returns to its caller.
+Individual phases retain full contained ticket guidance as a direct-reading fallback when this optional capability is absent; normal use does not load both routes.
+Eight physical guidance copies preserve contained portability; this extraction does not claim elimination of all duplication or measured context/behavior improvement.
 
 ## Dependencies and workflow tools
 The Skills are Markdown instructions: use an agent that can load them and your project's own development tools. No package installation or build is required for the Skills.
@@ -47,14 +50,11 @@ The Skills are Markdown instructions: use an agent that can load them and your p
 | Entire, optional | Capture session context and connect it to checkpoints. | Verify support for your agent and worktree; link only observed session/checkpoint IDs to the task. |
 
 **Handoff:** user prompt → task with scope and acceptance criteria → execution → evidence, status, and next action recorded in Beads → restart prompt with task ID.
-The next session rereads the task: Beads is task truth, not the prompt or a notebook.
-Beads adoption is conditional; once chosen, missing access or a failed claim blocks implementation, not permission to continue untracked. Without Beads, agree another tracking approach.
+The next session rereads the task: Beads is task truth, not the prompt or a notebook. Beads adoption is conditional; once chosen, missing access or a failed claim blocks implementation, not permission to continue untracked. Without Beads, agree another tracking approach.
 Entire captures context, not task truth or acceptance; no tool grants permission to commit, push, or close tasks.
 See the [integration guide](https://github.com/bioinfornatics/agentic-development/blob/develop/docs/integrations.md) for setup checks and boundaries.
-
 ## Learn more
 - [Development cycle](https://github.com/bioinfornatics/agentic-development/blob/develop/docs/cycle.md): how the phases fit together.
 - [Integrations](https://github.com/bioinfornatics/agentic-development/blob/develop/docs/integrations.md): Beads, Git, Entire, and optional Goose observation hooks.
 - [Contributing](https://github.com/bioinfornatics/agentic-development/blob/develop/docs/contributing.md): improve the method on develop.
-
 The main branch contains the generated installation package; develop contains its source and documentation. Both use this same README. Skills need no build; optional observation hooks require Python 3.10+ and use only the standard library.

skills/cycle/SKILL.md

@@ -66,9 +66,17 @@ a previous permission. This is an agent instruction, not a runtime cache.
    assumptions. A request to implement this slice authorizes its scoped code changes,
    not Git commits, remote operations, production actions or unrelated work.
 
-   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.
+   Before creating or repairing task descriptions or acceptance criteria, verify
+   current scope and write authority. Conditionally Load `agentic-development:task-authoring`
+   using the host's available Skill-loading mechanism (not a shell command), with
+   established goal, scope, criteria, native tracker context and current authority.
+   Reuse its guidance when already available and current; do not load both routes
+   normally. If the optional capability is unavailable, apply contained
+   [ticket authoring](references/ticket-authoring.md) directly and report direct
+   reading, not activation; do not retry loading or block routine work on its absence.
+   For routine reads, claims, progress updates or closure, do not load task-authoring.
+   Resume this caller after verified ticket readback or an explicit proposal/error;
+   retain this phase's scope, ownership, review and evidence gates.
    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.

skills/implement/SKILL.md

@@ -42,9 +42,17 @@ a previous permission. This is an agent instruction, not a runtime cache.
 
    Verify repository root, local instructions, tools and task goal.
 
-   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.
+   Before creating or repairing task descriptions or acceptance criteria, verify
+   current scope and write authority. Conditionally Load `agentic-development:task-authoring`
+   using the host's available Skill-loading mechanism (not a shell command), with
+   established goal, scope, criteria, native tracker context and current authority.
+   Reuse its guidance when already available and current; do not load both routes
+   normally. If the optional capability is unavailable, apply contained
+   [ticket authoring](references/ticket-authoring.md) directly and report direct
+   reading, not activation; do not retry loading or block routine work on its absence.
+   For routine reads, claims, progress updates or closure, do not load task-authoring.
+   Resume this caller after verified ticket readback or an explicit proposal/error;
+   retain this phase's scope, ownership, review and evidence gates.
 
    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;

skills/iterate/SKILL.md

@@ -48,9 +48,17 @@ a previous permission. This is an agent instruction, not a runtime cache.
    resuming artifact claims or executing consequential actions; verify current
    permission for the intended action, not historical approval.
 
-   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.
+   Before creating or repairing task descriptions or acceptance criteria, verify
+   current scope and write authority. Conditionally Load `agentic-development:task-authoring`
+   using the host's available Skill-loading mechanism (not a shell command), with
+   established goal, scope, criteria, native tracker context and current authority.
+   Reuse its guidance when already available and current; do not load both routes
+   normally. If the optional capability is unavailable, apply contained
+   [ticket authoring](references/ticket-authoring.md) directly and report direct
+   reading, not activation; do not retry loading or block routine work on its absence.
+   For routine reads, claims, progress updates or closure, do not load task-authoring.
+   Resume this caller after verified ticket readback or an explicit proposal/error;
+   retain this phase's scope, ownership, review and evidence gates.
 
    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;

skills/judge/SKILL.md

@@ -48,9 +48,17 @@ a previous permission. This is an agent instruction, not a runtime cache.
    resuming artifact claims or executing consequential actions; verify current
    permission for the intended action, not historical approval.
 
-   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.
+   Before creating or repairing task descriptions or acceptance criteria, verify
+   current scope and write authority. Conditionally Load `agentic-development:task-authoring`
+   using the host's available Skill-loading mechanism (not a shell command), with
+   established goal, scope, criteria, native tracker context and current authority.
+   Reuse its guidance when already available and current; do not load both routes
+   normally. If the optional capability is unavailable, apply contained
+   [ticket authoring](references/ticket-authoring.md) directly and report direct
+   reading, not activation; do not retry loading or block routine work on its absence.
+   For routine reads, claims, progress updates or closure, do not load task-authoring.
+   Resume this caller after verified ticket readback or an explicit proposal/error;
+   retain this phase's scope, ownership, review and evidence gates.
 
    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;

skills/plan/SKILL.md

@@ -57,9 +57,17 @@ a previous permission. This is an agent instruction, not a runtime cache.
    capabilities produce an explicit blocker, never simulated execution evidence.
    Use the coordinator's verified slice state when available; do not fabricate execution or acceptance.
 
-   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.
+   Before creating or repairing task descriptions or acceptance criteria, verify
+   current scope and write authority. Conditionally Load `agentic-development:task-authoring`
+   using the host's available Skill-loading mechanism (not a shell command), with
+   established goal, scope, criteria, native tracker context and current authority.
+   Reuse its guidance when already available and current; do not load both routes
+   normally. If the optional capability is unavailable, apply contained
+   [ticket authoring](references/ticket-authoring.md) directly and report direct
+   reading, not activation; do not retry loading or block routine work on its absence.
+   For routine reads, claims, progress updates or closure, do not load task-authoring.
+   Resume this caller after verified ticket readback or an explicit proposal/error;
+   retain this phase's scope, ownership, review and evidence gates.
 
    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;
@@ -158,19 +166,14 @@ a previous permission. This is an agent instruction, not a runtime cache.
    them inline by default; save only at an explicitly authorized destination.
 
    Create or update issues only when requested/authorized in the agreed tracker.
-   Inspect existing issues first, reuse matching work, verify supported fields and
-   write goals, exclusions, criteria, dependencies, ownership and restart context.
-   On updates, consolidate current solution/steps/files rather than append competing
-   designs; move dated findings to notes, preserve criterion IDs/history, reconcile
-   native edges and check cycles. Readback must pass the human readability gate in
-   ticket-authoring.md, not merely confirm nonempty fields.
-   Include Research's verified task-specific reading references: files or authorized
-   local web captures, entrypoints/sections, reasons, order, source identity and
-   freshness/accessibility limits. Do not copy full research into tickets or invent
-   saved resources; record local-only pointers honestly.
-   Distinguish parent hierarchy from prerequisites. After each write, read back
-   the issue and verify fields/edges; report actual IDs and errors. If writes are
-   not authorized, return proposed tickets without claiming they were created.
+   Use the conditional task-authoring route above with the established planning
+   baseline; do not repeat its procedure here. It must consolidate current solution/steps/files,
+   preserve criteria/history and native ownership/edges, and read back actual writes.
+   Supply Research's verified task-specific reading references, source identity,
+   order and freshness/accessibility limits; do not invent saved resources.
+   Retain planning scope, review requirements and verification proof. Distinguish
+   parent hierarchy from prerequisites; report actual IDs and errors, or proposed
+   tickets when writes are unavailable. Task authoring does not approve this plan.
 
    Verify actual delegated planning completion, source identity and result locator
    before integration. Reconcile conflicts and retain unresolved decisions and missing

skills/research/SKILL.md

@@ -50,9 +50,17 @@ a previous permission. This is an agent instruction, not a runtime cache.
      sources. Missing roadmap information is explicit; do not invent goals or expand
      bounded research to fill hierarchy labels. Resolve decision-blocking context
      only; roadmap proposals belong to requested planning or a decision-blocking need.
-   - 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.
+   - Before creating or repairing task descriptions or acceptance criteria, verify
+     current scope and write authority. Conditionally Load `agentic-development:task-authoring`
+     using the host's available Skill-loading mechanism (not a shell command), with
+     established goal, scope, criteria, native tracker context and current authority.
+     Reuse its guidance when already available and current; do not load both routes
+     normally. If the optional capability is unavailable, apply contained
+     [ticket authoring](references/ticket-authoring.md) directly and report direct
+     reading, not activation; do not retry loading or block routine work on its absence.
+     For routine reads, claims, progress updates or closure, do not load task-authoring.
+     Resume this caller after verified ticket readback or an explicit proposal/error;
+     retain this phase's scope, ownership, review and evidence gates.
 
    - 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;