home-v1-skills-code-agent/corp-v1-channel-architecture
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: require structured task contracts

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-02 12:36:14 +00:00
parent 091617ffe8
commit a7efaf86fe
2 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+1 -1
View File
@@ -208,7 +208,7 @@ Architecture owns complete Task decomposition for every Feature allocated to the
2. define at least two independently executable Tasks per Feature unless a recorded Architecture rationale proves that one atomic Task is the smallest verifiable boundary; 2. define at least two independently executable Tasks per Feature unless a recorded Architecture rationale proves that one atomic Task is the smallest verifiable boundary;
3. map the Feature's Tasks collectively to every acceptance outcome and every applicable requirement, with reciprocal canonical traceability; 3. map the Feature's Tasks collectively to every acceptance outcome and every applicable requirement, with reciprocal canonical traceability;
4. encode within-Feature sequencing and every cross-Feature prerequisite as acyclic Task dependencies; 4. encode within-Feature sequencing and every cross-Feature prerequisite as acyclic Task dependencies;
5. give each Task one specific outcome, bounded scope, repository/component owner, future acceptance-evidence requirement, and canonical/display identity; 5. give each Task one specific outcome, repository/component owner, canonical/display identity, task-specific implementation artifacts, concrete inputs and outputs, failure boundaries, exclusions, verification steps, and future acceptance-evidence requirements;
6. keep draft Tasks separate from implementation approval and Kanban Focus admission. 6. keep draft Tasks separate from implementation approval and Kanban Focus admission.
Architecture must not report planning readiness while any Feature allocated to the release lacks this complete Task breakdown. A Feature-shaped placeholder Task, a generated empty Task group, or requirement coverage without executable Tasks does not satisfy the gate. Architecture must not report planning readiness while any Feature allocated to the release lacks this complete Task breakdown. A Feature-shaped placeholder Task, a generated empty Task group, or requirement coverage without executable Tasks does not satisfy the gate.
tests/test_task_breakdown_policy.py
+6 -1
View File
@@ -24,7 +24,12 @@ class TaskBreakdownPolicyTest(unittest.TestCase):
required = [ required = [
"version: 1.7.0", "version: 1.7.0",
"repository/component owner", "repository/component owner",
"future acceptance-evidence requirement", "acceptance-evidence requirements",
"implementation artifacts",
"inputs and outputs",
"failure boundaries",
"exclusions",
"verification steps",
"within-Feature sequencing", "within-Feature sequencing",
"cross-Feature prerequisite", "cross-Feature prerequisite",
"acyclic Task dependencies", "acyclic Task dependencies",