Skip to content

lidge-jun/codexclaw / plugins/codexclaw/skills/pabcd

cxc-pabcd

Verified

Use for Plan-Audit-Build-Check-Done work. Triggers: PABCD, plan this, 기획, 단계별로, 요구사항 정리.

references/implementation-units.md

View on GitHub
### Implementation-Unit Documents

Full documentation routine (P concretizes the docs, A audits them as a hard gate, D
archives to `_fin/`, plus the mainstream design-doc/RFC translation table):
[Implementation log](../../dev-scaffolding/references/implementation-log.md).

**DIFFLEVEL-ROADMAP-01 (STRICT).** For any multi-phase unit
(2+ work-phases), the FIRST P — or the dedicated design-only Phase-0 pass — must
deliver the entire roadmap concretized: `000_plan.md` (objective, constraints,
dependency-ordered work-phase map) PLUS every phase's decade doc written to full
diff-level precision (exact paths, NEW/MODIFY/DELETE, before/after diffs) — each one
a copy-paste-executable PRD, not an outline. Scaffolding empty decade files to "fill
per cycle" does NOT satisfy this rule. Each later cycle's P starts from its
pre-written doc: re-verify it against the current codebase (stale check — earlier
phases may have moved lines, signatures, or files), amend the doc, then execute.
For prior D direction, follow [loop continuity](../../loop/SKILL.md)
(LOOP-CONTINUITY-01).

**LEXICO-SPLIT-01 (DEFAULT).** Use numeric lexicographic prefixes for unit documents;
keep research/spec material in the 000-range and implementation designs in decade
ranges. Keep them separate: no implementation diffs inside research documents or
survey padding inside a phase plan. Audit this separation. Naming deviations follow
[dev rule classes](../../dev/SKILL.md), rather than a universal safety failure;
the runtime P→A gate still requires an existing directory with a numbered plan file.

**UNIT-RESIDENCE-01 (DEFAULT).** C2+ development belongs to an
implementation unit (`<cxc devlog path>/_plan/YYMMDD_slug/`; `devlog/_plan/` in repo mode). Ceremony scales with class.
C0/C1 record behavior is canonically defined by [cxc-dev §0.1](../../dev/SKILL.md):
C0 is exempt from numbered unit records; C1 records in the owning unit only when
one already exists. Do not create a unit solely for a C0/C1 fast-path record.
This exception does not waive verification, safety, or behavior-based promotion.
When residence is required and no unit exists, use the existing repository's
unit convention; interview resolves placement when interview is in scope.

Devlog plan artifacts use decade-range numbering to separate concerns:

| Range | Purpose | Examples |
|-------|---------|----------|
| 000-009 | Research, specs, MOC | `000_plan.md`, `001_api_survey.md`, `002_competitor_analysis.md` |
| 010-019 | Phase 1 | `010_phase1_auth_module.md`, `011_phase1_db_schema.md` |
| 020-029 | Phase 2 | `020_phase2_frontend.md` |
| 030-039 | Phase 3 | ... |

Rules:
- 000-range durable research is mandatory for C4, and for C3 when cross-turn,
  contract, architecture, or repository-convention needs require it. It is optional
  for C0-C2 and low-persistence C3. C2+ still follows UNIT-RESIDENCE-01;
  C0/C1 follows cxc-dev §0.1 without a forced new unit.
- Default: sequential within decade (`000`, `001`, `002`...).
- Overflow (>10 docs in a range): use sub-index (`000_0_name.md`, `000_1_name.md`).
- This repo uses three-digit prefixes (`000_`, `010_`, `020_`); keep the convention
  rather than mixing two-digit names.

## Loop routes

Before multi-cycle entry, read [docs-first timing](../../loop/SKILL.md)
(LOOP-DOCS-FIRST-01); roadmap content is defined above.
Before adding an in-scope unit mid-loop, follow [plan amendments](plan-output.md)
and the [goalplan schema](../../loop/references/durable-goalplan.md)
(LOOP-UNIT-CHAIN-01). Do not extend the agreed objective.
For divergence and collapse, read [divergence tiers](../../loop/references/divergence-tiers.md).
Faithful execution and PLAN-TRACK-01 remain in
[Work-phase loop](../SKILL.md#work-phase-loop-multi-pass-tasks).
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall